)Jeremy Thomerson wrote:
On Tue, Jun 15, 2010 at 6:58 PM, James Carman <ja...@carmanconsulting.com>wrote:
I believe that repository is for software published by the ASF, but I
could be wrong.
He wants us to deploy Wicket to it, so I think that fits the bill. :)
I'm +1 for this. I'll do the committer part with the help of Michael.
Let's see if anyone has an objection. Michael, could you open a JIRA for
this and attach a patch for our pom? If nobody has an objection, I'll work
on it later in the week.
https://issues.apache.org/jira/browse/WICKET-2918
I've created an issue and will attach the modified pom's hopefully by
tomorrow. My thinking is that only future releases need to be handled
so I will create new snapshot and release profiles in the 1.4.x branch
and the 1.5 trunk to handle the snapshots right now and to support the
next releases.
For the snapshots the apache build cluster job definition would need to
be modified with the appropriate server credentials to be able to deploy
the snapshot artifacts. I also found out that the nexus repository
supports auto removal of older snapshots (I think it will keep the last
3) and will remove all the snapshots when a matching release is made.
So the <uniqueVersion>false<uniqueVersion> flag is no longer needed and
apparently maven 3.0 removes support for this tag anyways.
I've looked at a couple of the other apache projects that were setup to use the
apache nexus repository and most of the have a parent pom of the
org.apache.apache artifact version 7.
http://svn.apache.org/repos/asf/maven/pom/tags/apache-7/pom.xml
But I will try and figure out a profile that incorporates this definition
without needing the parent pom to be defined.
Also the ticket (https://issues.apache.org/jira/browse/INFRA-1896) asks that
sub issues include a link (like through nabble) to the vote on switching over
to the nexus managed repository.
Regards,
Mike
