+1 The only problem I can see with this atm is the definition of the assembly plugin which caused us a lot of trouble in the Pluto release. Once the assembly plugin is configured in the parent pom, child poms are not able to override it (this will be fixed in an upcomming release, however today this can be a pain if you have different modules with different assemblies). But that's a minor issue we can sort out.
Regards Carsten 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 > -- Carsten Ziegeler cziege...@apache.org
