I have used repository.a.o for preparing the Shindig release, and can
confirm, bar the issues of having the GPG and ssh/svn passwords in the
settings.xml every thing works just fine and it makes it a lot easier.
(fortunately as I have done it a lot of times now :) )
The settings.xml issues can be dealt with in a number of ways
including putting it on a small encrypted loopback disk image. I just
edit it, and remember to reset and then clean the history.
Ian
On 20 May 2009, at 23:19, Felix Meschberger wrote:
Hi all,
Lets pick up the repository.a.o discussion again now that we have
released Sling 5.
I have created a patch for our parent pom and attached it to the
tracker
issue SLING-917 [1]. The important changes:
* Use Apache parent pom 6
* Drop most of our apache-release profile
(formerly known as release profile)
* Drop some plugins in the pluginManagement section
* Drop repositories and pluginRepositories sections
Using the Nexus repository at repository.a.o has the massive advantage
that the release process is drastically simplified: A release is
uploaded to a staging repository where it can be reviewed for the
vote.
When the vote has passed, the staging repository can easily be
deployed.
There is a catch to this, though: The SVN password and GPG passphrase
have to be stored in the Maven 2 settings file for the release process
to work correctly. Starting with Maven 2.1 the SVN password file is
said
to be supported in encrypted form, but the GPG passphrase issue still
remains.
Weighing the advantages against the disadvantages, I tend to prefer
the
ease of deployment in this case.
Next steps after discussion :
* Vote on this issue
* Have the repository.a.o team setup Sling for Nexus deployment
* Release the Sling parent pom 6
* Update references in projects to the new parent pom
* and so on ...
WDYT ?
Regards
Felix
[1] https://issues.apache.org/jira/browse/SLING-917
