[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16128: ---------------------------------------- The whole purpose of relying to Nexus is to reduce the amount of maintainance/gouvernance we have when it comes to publishing stuff. If we can rely on standard Maven mechanism, we provide more portability, with less effort. The goal is first to see the issues that we'll have at publication (such as colliding versions). It's a first step. Ultimately, we'll also try to consume these Nexus site for aggregation. Point is to publish SNAPSHOTs in a first time, through the CI jobs. Just that will require projects to start working on releasing their own "Final" as dealing with version is a necessary step in that direction. Nexus URLs are a bit ugly, that probably won't be the one we'll provide to end-users. If we go for a "build-on-nexus" approach, we'll probably release stuff by mirroring the output of Nexus to a nicer location, such as the ones we're using now. Remove necessity to maintain: * publish.sh * URL conventions and many stuff related to publication of CI builds First, I would test it only for SNAPSHOTs. Component developers will learn that they need to take care of not having the same version on different streams. That would already be a great step forward. Then we may be interested in teaching them how to release their own component, but I see that as a secondary step, after simply publishing of SNAPSHOTs on Nexus. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira