Re: [DISCUSS] Use repository.a.o for deployments

2009-05-21 Thread Carsten Ziegeler
+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

Re: [DISCUSS] Use repository.a.o for deployments

2009-05-21 Thread Juan José Vázquez Delgado
Next steps after discussion :   * Vote on this issue +1 Regards, Juanjo.

[DISCUSS] Use repository.a.o for deployments

2009-05-20 Thread Felix Meschberger
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

Re: [DISCUSS] Use repository.a.o for deployments

2009-05-20 Thread Ian Boston
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