Community
Participate
Working Groups
Follow on to bug 413172 (Nexus instance for LT repo.locationtech.org) we have two community issues on the handling of maven repository striation and versioning of dependency subsets (introduced by the CQ process): * https://locationtech.org/bugs/show_bug.cgi?id=27 Define URL for maven stable / snapshot repositories * https://locationtech.org/bugs/show_bug.cgi?id=25 Deploy jcommon-1.0.16-CQ7581.jar (example subset dependency) Email discussion of these two issues resulted in the request to engage the Architecture Committee on this subject. Several location tech projects are destined to be used as a library by the wider Java community and are thus expected to respect maven central conventions: * http://maven.apache.org/guides/mini/guide-central-repository-upload.html * https://docs.sonatype.org/display/Repository/Choosing+your+Coordinates We are trying to strike a balance between transparency (when a dependency subset is required) and ease-of-use for java developers in the wider community. Research: * https://wiki.eclipse.org/Services/Nexus * bug 288644 Decide of group ids for Eclipse Maven artifacts * bug 283745 Provide Maven repositories of stuff built at Eclipse
Quick chat with architecture committee resulting in further discussion moving to the location tech mailing list. The Eclipse Bundle Recipes project (http://eclipse.org/proposals/rt.ebr/) was offered as another venue which has struggled with group id naming. This makes sense as tycho ties these OSGi build target and maven repository world together :) The general arc of discussion made more sense in summary: * LocationTech Bug 27 -> Defining of groupId * LocationTech Bug 25 -> Defining version (when distributing a CQ subset) * LocationTech Bug 28 -> GroupId / Namespace for scala project
Discussion has settled down, resulting in the following tips and tricks for the LocationTech maven repository: * https://locationtech.org/wiki/The_Nexus TLDR: Use of CQ number as a classifier to isolate use of subsets (similar to Orbit). use of maven profile to switch between original jar and CQ subset during deploy.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This issue has been migrated to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/179.
