|
Mail sent on the 08/21 and
apparently lost. Best regards,
Thierry Boileau -- Restlet ~ Core developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com |
--- Begin Message ---Hi Bruno,is the org.jssutils package hosted in our Maven repos the same than the one hosted in the central one? If this is the case, I think we can remove it from our Maven repository which is simpler.best regards, Thierry BoileauHello,I've just realised that the groupId values used by the build script (for Maven2 packaging) were actually those used by the original projects. For example, it creates POMs for groupId "org.jsslutils", whereas I've used "org.jsslutils" for the "official" bundles I've produced for that project (to be published in the central repository).I'm a bit concerned this may conflict with the versions from the central repository when they are available. In the case of jsslutils (although version 0.5 isn't in the central repository yet), the POM generated by the Restlet build file removes some information, such as the location of the source, etc.Because the build script effectively repackages many libraries that may also be more officially packaged in the central Maven repository, I think the guidelines at [1] should be used, in particular the FAQ "I have a patched version of the foo project developed at foo.com, what groupId should I use?" (even if it's not strictly speaking patched).This could lead to things like: <groupId>org.restlet</groupId> <artifactId>org.jsslutils-jsslutils</artifactId> or some variants: <groupId>org.restlet.external</groupId> <artifactId>org.jsslutils-jsslutils</artifactId> ... <groupId>org.restlet</groupId> <artifactId>external-org.jsslutils-jsslutils</artifactId> I'm not sure what's best. Best wishes, Bruno.[1] http://maven.apache.org/guides/mini/guide-central-repository-upload.html
--- End Message ---
