-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JCL-321: Use com.inrupt.client for Maven groupId #401
Conversation
Looks good. Another (arguably better) option would be to leave A bit cleaner, a bit more work. This works too, for all practical purposes almost the same thing. |
Documentation will need some updates. |
I had also been considering the creation of an independent "parent" project, living in its own repo. Then that parent can be consumed by all Java projects in Inrupt, including these client library. That change would basically involve moving most of the current root pom.xml into a separate repo and then just consuming that from here. |
@hzbarcea the pattern you describe is something I see quite a bit elsewhere. What do you see as the advantage of having a special |
You are correct. My personal preference is to have that separation, but I recognize that it's quite subjective. |
Pressed too fast. The second topic you mentioned (separate and orthogonal): having a parent project for all java projects, is imho more interesting and maybe more important. That would ensure a consistent dependency management across all (or most) java projects. It would make many things easier (faster, cheaper, better) in terms of versions baseline management, upgrades, testing, deviations from baseline. It could be done at any time though, but the earlier the better. |
This changes the groupId of the client libraries from
com.inrupt
tocom.inrupt.client