Re: maven-release-manager/src/main/components-fragment.xml

2013-07-08 Thread Olivier Lamy
see the pom: http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/pom.xml plexus-maven-plugin merge the content I agree that's not the usual place :-) 2013/7/9 Chris Graham : > Hi All. > > The full path is: > http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-

maven-release-manager/src/main/components-fragment.xml

2013-07-08 Thread Chris Graham
Hi All. The full path is: http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/src/main/components-fragment.xml Can someone please explain to me how this file is used (and why it's not under the META-INF/plexus dir [at the very least]) ? I'm struggling to see how it is incor

Re: [RESULT] [VOTE] Apache Maven War plugin 2.4

2013-07-08 Thread Baptiste MATHUS
I remember seeing some tweets around friday last week about this. Maybe there's still an issue in central syncing? I've also a release waiting for syncing from mojo, but a bit more recent than yours (only 7 hours ago) so I'm not really worrying yet since we're told to wait around 24h max. My 2 ce

Re: [RESULT] [VOTE] Apache Maven War plugin 2.4

2013-07-08 Thread Olivier Lamy
FYI. I hit the release button on repository.a.o but that's still not synced so waiting before sending announce email. 2013/7/7 Olivier Lamy : > The vote has passed with the following result: > +1 (binding): Hervé, Robert, Stéphane, Olivier > +1 (non binding): Baptiste > -1 (non binding): sebb > >

Re: git commit: upgrade to rat:0.9 and defensively prepare for maven-parent 24

2013-07-08 Thread Stephen Connolly
You haven't updated the site either... it's still 0.9-SNAPSHOT. If your release process leaves the -SNAPSHOT site deployed then your release process is broken ;-) On 8 July 2013 11:17, sebb wrote: > On 8 July 2013 10:36, wrote: > > Updated Branches: > > refs/heads/master 7bb5f1957 -> 50a24e

Re: git commit: upgrade to rat:0.9 and defensively prepare for maven-parent 24

2013-07-08 Thread sebb
On 8 July 2013 10:36, wrote: > Updated Branches: > refs/heads/master 7bb5f1957 -> 50a24e541 > > > upgrade to rat:0.9 and defensively prepare for maven-parent 24 Warning: RAT 0.9 is a lot slower than 0.8 when scanning large files that don't have a valid license. Make sure it does not try to sca

Re: Java version compatibility

2013-07-08 Thread Arnaud Héritier
let's do that. I'll test it on archetype level and then we'll see to move it later on plugins or maven levels On Mon, Jul 8, 2013 at 11:02 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I think ultimately at maven parent, but if you want to play at a less wide > level first I t

Re: Java version compatibility

2013-07-08 Thread Stephen Connolly
I think ultimately at maven parent, but if you want to play at a less wide level first I think that could be a good plan too On 8 July 2013 09:59, Arnaud Héritier wrote: > yes, far from me the idea to have such controls for every builds :-) > either in a dedicated profile launched manually by c

Re: Java version compatibility

2013-07-08 Thread Arnaud Héritier
yes, far from me the idea to have such controls for every builds :-) either in a dedicated profile launched manually by committers (and CI?) or in the release profile Something to add at which level ? plugins parent ? maven parent ? On Mon, Jul 8, 2013 at 10:52 AM, Stephen Connolly < stephen.alan

Re: svn commit: r1500602 - /maven/archetype/trunk/pom.xml

2013-07-08 Thread Arnaud Héritier
No it wasn't intended. Fucking subversion that has no staging feature. I lost the habit to work with it I revert the version change for wagon I will update the commit message for jenv because the change may be useful And now I stop to work on projects using SVN (I'm didn't use it for a to long time

Re: Java version compatibility

2013-07-08 Thread Stephen Connolly
On 8 July 2013 09:23, Arnaud Héritier wrote: > Hi, > > Last night I introduced by error a dependency requiring Java 6 in the > archetype plugin whereas we are always supposed to support Java 5 (Yes we > can :-) ) > Myself I don't have anymore a Java 5 on my computer and I'm often using > Java

Re: svn commit: r1500602 - /maven/archetype/trunk/pom.xml

2013-07-08 Thread sebb
On 8 July 2013 09:26, wrote: > Author: aheritier > Date: Mon Jul 8 08:26:19 2013 > New Revision: 1500602 > > URL: http://svn.apache.org/r1500602 > Log: > Revert commons-io upgrade. commons-io >= 2.3 requires Java6 or later while we > are always supporting Java 5 -1 The commit makes two other

Java version compatibility

2013-07-08 Thread Arnaud Héritier
Hi, Last night I introduced by error a dependency requiring Java 6 in the archetype plugin whereas we are always supposed to support Java 5 (Yes we can :-) ) Myself I don't have anymore a Java 5 on my computer and I'm often using Java 7 by default and I'm probably not the only one. Even if we

Re: svn commit: r1500547 - /maven/site/trunk/content/apt/docs/history.apt

2013-07-08 Thread sebb
Something lke this should do: svn:mime-type: text/plain; charset=utf-8 Adjust the charset as needed. On 8 July 2013 07:10, Hervé BOUTEMY wrote: > good idea: I hate these broken log messages, but as they are only log > messages, I didn't dig into it > > Le lundi 8 juillet 2013 02:04:18 sebb a éc