Hi Karel, Thanks for the suggestion to use classifiers, that sounds appropriate for Restlet editions. I entered a RFE: http://restlet.tigris.org/issues/show_bug.cgi?id=1182
However, the current mechanisms ensures that all extensions have a separate artifact for each edition, based on the parent's groupID. It may not be ideal compared to classifiers but it does seem to work. Am I missing your point? Best regards, Jerome -- Restlet ~ Founder and Technical Lead ~ http://www.restlet.org Noelios Technologies ~ http://www.noelios.com -----Message d'origine----- De : Karel Vervaeke [mailto:[email protected]] Envoyé : vendredi 2 juillet 2010 22:37 À : [email protected] Objet : Maven distribution problem (short version) When building the 'gae' restlet edition, you have a separate groupId for the restlet 'core' artifact (org.restlet.gae:org.restlet instead of org.restlet.jse:org.restlet), which is nice. Unfortunately, the 'gae' edition also introduces changes in org.restlet:org.restlet.ext.servlet (via ifdef/ifndef instructions). So depending on the edition, you have different 'editions' of the same maven artifact, which Maven doesn't like. It might be better (though I didn't examine the details) to use maven's classifier mechanism for distinguishing the maven artifacts This page does a good job at describing maven classifiers: http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-platform-classifier.html Does this make sense? Karel ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2628761 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2659736
