Hi, I've summarized the procedures there: http://contrib.xwiki.org/xwiki/bin/view/Main/#HRequestingsnapshostbuildsfory... Let me know if some things remain unclear. There's a live example with xwiki-plugin-excel * http://hudson.xwiki.org/job/xwiki-plugin-excel/ * http://maven.xwiki.org/snapshots/org/xwiki/contrib/xwiki-plugin-excel/ * http://maven.xwiki.org/releases/org/xwiki/contrib/xwiki-plugin-excel/ Thanks, JV. On Tue, Mar 16, 2010 at 3:16 PM, Jean-Vincent Drean <[email protected]> wrote:
Hi,
I've discussed about it a bit more with Jerome and I'd like to come with a simpler proposal. Contrib releases would be published in http://maven.xwiki.org/releases/org/xwiki/contrib/, the only difference with official xwiki.org releases is that the distributionManagement configuration in contrib project would point to nexus staging repo.
About contrib snapshots they'd use the same configuration as official xwiki.org projects, contributors would ask on the list for their project to be added on http://hudson.xwiki.org.
Here's my +1
Thanks, JV.
On Wed, Mar 10, 2010 at 3:17 PM, Jean-Vincent Drean <[email protected]> wrote:
Hi XWikiers,
The goal of this proposal is to be able to deploy contrib projects on the xwiki maven repository, allowing distributions to depend on contrib projects. Contrib projects deployment must be different from the other xwiki.org deployments since want to review the artifacts contributors publish under our banner.
The proposal is to use the nexus staging deployment feature to perform contrib releases. Strategy:
- Create the http://maven.xwiki.org/contrib/ repository - When a contributor first want to release his project, create a user for him allowed to push artifacts in staging on nexus.xwiki.org. This credentials are meant to be put in ~/.m2/settings.xml to be used by maven for authentication on nexus.xwiki.org. - When a contributor performs a release the artifacts are pushed on the nexus staging repository, an email is sent on [email protected] to notify nexus admins that they must review/publish them.
We could create a new http://svn.xwiki.org/svnroot/xwiki/contrib/pom/ pom project to ease maintainers work, here's a draft:
-------------------------8<----------------------------- <groupId>org.xwiki.contrib</groupId> <artifactId>root</artifactId> <name>XWiki Contrib - Root POM</name> <packaging>pom</packaging> <version>1.0-SNAPSHOT</version> <url>http://contrib.xwiki.org</url> <issueManagement> <system>jira</system> <url>http://jira.xwiki.org/jira/browse/XCONTRIB</url> </issueManagement> <scm> <connection>scm:svn:http://svn.xwiki.org/svnroot/xwiki/contrib/pom/trunk</connection> <developerConnection>scm:svn:https://svn.xwiki.org/svnroot/xwiki/contrib/pom/trunk</developerConnection> <url>http://svn.xwiki.org/svnroot/xwiki/contrib/pom/trunk</url> </scm> <distributionManagement> <repository> <id>xwiki-staging</id> <name>XWiki Staging Repository</name> <url>http://nexus.xwiki.org/nexus/service/local/staging/deploy/maven2/</url> </repository> </distributionManagement> ------------------------->8-----------------------------
Note: I'm still not sure about this, I think duplicating distributionManagement in an application and have xwiki-applications as parent might be more convenient than the contrary (duplicating build extensions and stuff + have org.xwiki.contrib.root as parent).
WDYT ?
Thanks, JV.