10 Mar
2010
10 Mar
'10
3:47 p.m.
On Wed, Mar 10, 2010 at 3:37 PM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
Not sure either, I thought about xwiki-contrib too but found weird to
duplicate the groupId in the artifactId.
Anyway I don't have a strong opinion about this, proposals anyone ?
Yes that's exactly what we need, I didn't know that maven 3 had this
feature, nice! We could wait for it before introducing this project.
JV.
On Wed, Mar 10, 2010 at 15:17, Jean-Vincent Drean
<jv(a)xwiki.com> wrote:
WDYT about devs(a)xwiki.org ?
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
notifications(a)xwiki.org to notify nexus admins that they must
review/publish them.
That's not really just a notification then, there is too much things
in notifications(a)xwiki.org, it should probably be a specialized
mailing list.
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>
Not sure about the name. "contrib" or "xwiki-contrib" would be better
i think. <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).
What we would really need in the kind of multi parent (don't remember
the real name) maven 3 has.