Re: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Anders Hammar
Will the svn repo go read only once we switch, to prevent mistakes?

/Anders


On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
kristian.rosenv...@gmail.com> wrote:

> The repos are located at:
>
> https://git-wip-us.apache.org/repos/asf/maven.git
> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>
>
> Please "test" them, unless anyone has any objections they will become
> r/w 24 hours from now.
>
>
> The "3.1.0" tag is in the git repo, so I suppose this does not affect
> the release unless we have to respin.
>
>
> Kristian
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Olivier Lamy
Yup and already read only now.

--
Olivier
Le 28 nov. 2012 09:00, "Anders Hammar"  a écrit :


Re: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Kristian Rosenvold
SVN is read only while we test, this is standard procedure for migrations.

(So if you *must* work on core in the next 24 hours, github is the
place to do it ;)

Kristian



2012/11/28 Anders Hammar :
> Will the svn repo go read only once we switch, to prevent mistakes?
>
> /Anders
>
>
> On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
> kristian.rosenv...@gmail.com> wrote:
>
>> The repos are located at:
>>
>> https://git-wip-us.apache.org/repos/asf/maven.git
>> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>>
>>
>> Please "test" them, unless anyone has any objections they will become
>> r/w 24 hours from now.
>>
>>
>> The "3.1.0" tag is in the git repo, so I suppose this does not affect
>> the release unless we have to respin.
>>
>>
>> Kristian
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Anders Hammar
+1 (non-binding)

Did some smaller text fixes to the two new doc pages and re-published. But
links to these pages are missing from the site.

/Anders


On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:

> Hi,
>
> Here is a link to Jira with 30 issues resolved:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-073/
>
> The distributable binaries and sources for testing can be found here:
>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>
> Specifically the zip, tarball, and source archives can be found here:
>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>
> Staging site:
> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>
> The documentation specifically for this release pertains to JSR330 and
> SLF4J-based logging:
> http://maven.apache.org/maven-jsr330.html
> http://maven.apache.org/maven-logging.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> People develop abstractions by generalizing from concrete examples.
> Every attempt to determine the correct abstraction on paper without
> actually developing a running system is doomed to failure. No one
> is that smart. A framework is a resuable design, so you develop it by
> looking at the things it is supposed to be a design of. The more examples
> you look at, the more general your framework will be.
>
> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Arnaud Héritier
But after the migration we remove them from SVN ?
Perhaps with just a README to let people where it was moved ?
Otherwise it will be really confusing and source of errors. No ?


On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold <
kristian.rosenv...@gmail.com> wrote:

> SVN is read only while we test, this is standard procedure for migrations.
>
> (So if you *must* work on core in the next 24 hours, github is the
> place to do it ;)
>
> Kristian
>
>
>
> 2012/11/28 Anders Hammar :
> > Will the svn repo go read only once we switch, to prevent mistakes?
> >
> > /Anders
> >
> >
> > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
> > kristian.rosenv...@gmail.com> wrote:
> >
> >> The repos are located at:
> >>
> >> https://git-wip-us.apache.org/repos/asf/maven.git
> >> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
> >>
> >>
> >> Please "test" them, unless anyone has any objections they will become
> >> r/w 24 hours from now.
> >>
> >>
> >> The "3.1.0" tag is in the git repo, so I suppose this does not affect
> >> the release unless we have to respin.
> >>
> >>
> >> Kristian
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
-
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aherit...@gmail.com
Twitter/Skype : aheritier


Re: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Kristian Rosenvold
This is where things get a little tricky ;) The first time we did this
I had the foresight to ask olivier to add a notice to the repository
about moving to git. This time I forgot, and we're read only now. Doh.

The svn repos are not deleted. I will ask infra if they can add a
notice to the r/o svn repos, maybe update standard procedure for this
too, since it's a shared problem.

Kristian




2012/11/28 Arnaud Héritier :
> But after the migration we remove them from SVN ?
> Perhaps with just a README to let people where it was moved ?
> Otherwise it will be really confusing and source of errors. No ?
>
>
> On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold <
> kristian.rosenv...@gmail.com> wrote:
>
>> SVN is read only while we test, this is standard procedure for migrations.
>>
>> (So if you *must* work on core in the next 24 hours, github is the
>> place to do it ;)
>>
>> Kristian
>>
>>
>>
>> 2012/11/28 Anders Hammar :
>> > Will the svn repo go read only once we switch, to prevent mistakes?
>> >
>> > /Anders
>> >
>> >
>> > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
>> > kristian.rosenv...@gmail.com> wrote:
>> >
>> >> The repos are located at:
>> >>
>> >> https://git-wip-us.apache.org/repos/asf/maven.git
>> >> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>> >>
>> >>
>> >> Please "test" them, unless anyone has any objections they will become
>> >> r/w 24 hours from now.
>> >>
>> >>
>> >> The "3.1.0" tag is in the git repo, so I suppose this does not affect
>> >> the release unless we have to respin.
>> >>
>> >>
>> >> Kristian
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: dev-h...@maven.apache.org
>> >>
>> >>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
> --
> -
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aherit...@gmail.com
> Twitter/Skype : aheritier

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2

2012-11-28 Thread Olivier Lamy
ok I will re spin the release due to this old blocker issue :P

2012/11/27 Ansgar Konermann :
> Please remove it.
>
> I've seen it slipping into way too many poms of corporate projects, just to
> add more noise to the poms and give maven a bad name for "being so hard to
> understand".
>
> So it as soon as possible.
>
> TIA + BR
>
> Ansgar
> Am 27.11.2012 21:46 schrieb "Olivier Lamy" :
>
>> 2012/11/27 Robert Scholte :
>> > Hi Olivier,
>> >
>> > looks like a very nice and useful archetype.
>> > the configuration of the m-invoker-p could be smaller, since it includes
>> > some defaults.
>> >
>> > There's only one thing which always surprises me: why is the url filled
>> with
>> > our site?
>> marketing ? :-)
>> more seriously I have no idea about the history.
>> perso I don't have any trouble with that.
>> Folks can remove that (and must if they deploy a web site)
>> > I've seen a lot of projects started with archetypes and they all keep
>> this
>> > url untouched.
>> >
>> > I'd prefer to remove it, since it's almost never pointing to the
>> > project-page.
>> >
>> > -Robert
>> >
>> >
>> > Op Tue, 27 Nov 2012 00:54:58 +0100 schreef Olivier Lamy <
>> ol...@apache.org>:
>> >
>> >> Hi,
>> >>
>> >> I'd like to release the archetype for maven plugin.
>> >> The goal is to have an archetype which generate project using new mojo
>> >> annotations (and a sample to run maven-invoker-plugin)
>> >> We fixed 2 issues:
>> >> http://jira.codehaus.org/browse/MARCHETYPES/fixforversion/18708
>> >>
>> >> Staging repository:
>> >> https://repository.apache.org/content/repositories/maven-080/
>> >>
>> >> To test it:
>> >> mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes
>> >> -DarchetypeArtifactId=maven-archetype-plugin -DarchetypeVersion=1.2
>> >>
>> >> -DarchetypeRepository=
>> https://repository.apache.org/content/repositories/maven-080/
>> >>
>> >>
>> >> Vote open for 72 hours.
>> >>
>> >> [ ] +1
>> >> [ ] +0
>> >> [ ] -1
>> >>
>> >>
>> >> Thanks,
>> >> --
>> >> Olivier Lamy
>> >> Talend: http://coders.talend.com
>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 2)

2012-11-28 Thread Olivier Lamy
Hi,

I'd like to release the archetype for maven plugin.
The goal is to have an archetype which generate project using new mojo
annotations (and a sample to run maven-invoker-plugin)
We fixed 2 issues:
http://jira.codehaus.org/browse/MARCHETYPES/fixforversion/18708

Staging repository:
https://repository.apache.org/content/repositories/maven-089/

To test it:
mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes
-DarchetypeArtifactId=maven-archetype-plugin -DarchetypeVersion=1.2
-DarchetypeRepository=https://repository.apache.org/content/repositories/maven-089/


Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


Thanks,
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2

2012-11-28 Thread Anders Hammar
Should we fix this in all applicable archetypes, and not just this one?
It's in the quickstart as well, and probably others.

/Anders


On Wed, Nov 28, 2012 at 9:44 AM, Olivier Lamy  wrote:

> ok I will re spin the release due to this old blocker issue :P
>
> 2012/11/27 Ansgar Konermann :
> > Please remove it.
> >
> > I've seen it slipping into way too many poms of corporate projects, just
> to
> > add more noise to the poms and give maven a bad name for "being so hard
> to
> > understand".
> >
> > So it as soon as possible.
> >
> > TIA + BR
> >
> > Ansgar
> > Am 27.11.2012 21:46 schrieb "Olivier Lamy" :
> >
> >> 2012/11/27 Robert Scholte :
> >> > Hi Olivier,
> >> >
> >> > looks like a very nice and useful archetype.
> >> > the configuration of the m-invoker-p could be smaller, since it
> includes
> >> > some defaults.
> >> >
> >> > There's only one thing which always surprises me: why is the url
> filled
> >> with
> >> > our site?
> >> marketing ? :-)
> >> more seriously I have no idea about the history.
> >> perso I don't have any trouble with that.
> >> Folks can remove that (and must if they deploy a web site)
> >> > I've seen a lot of projects started with archetypes and they all keep
> >> this
> >> > url untouched.
> >> >
> >> > I'd prefer to remove it, since it's almost never pointing to the
> >> > project-page.
> >> >
> >> > -Robert
> >> >
> >> >
> >> > Op Tue, 27 Nov 2012 00:54:58 +0100 schreef Olivier Lamy <
> >> ol...@apache.org>:
> >> >
> >> >> Hi,
> >> >>
> >> >> I'd like to release the archetype for maven plugin.
> >> >> The goal is to have an archetype which generate project using new
> mojo
> >> >> annotations (and a sample to run maven-invoker-plugin)
> >> >> We fixed 2 issues:
> >> >> http://jira.codehaus.org/browse/MARCHETYPES/fixforversion/18708
> >> >>
> >> >> Staging repository:
> >> >> https://repository.apache.org/content/repositories/maven-080/
> >> >>
> >> >> To test it:
> >> >> mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes
> >> >> -DarchetypeArtifactId=maven-archetype-plugin -DarchetypeVersion=1.2
> >> >>
> >> >> -DarchetypeRepository=
> >> https://repository.apache.org/content/repositories/maven-080/
> >> >>
> >> >>
> >> >> Vote open for 72 hours.
> >> >>
> >> >> [ ] +1
> >> >> [ ] +0
> >> >> [ ] -1
> >> >>
> >> >>
> >> >> Thanks,
> >> >> --
> >> >> Olivier Lamy
> >> >> Talend: http://coders.talend.com
> >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >> >
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: dev-h...@maven.apache.org
> >> >
> >>
> >>
> >>
> >> --
> >> Olivier Lamy
> >> Talend: http://coders.talend.com
> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >>
> >>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2

2012-11-28 Thread Olivier Lamy
https://svn.apache.org/r1414409
then
https://svn.apache.org/r1414421


2012/11/28 Anders Hammar :
> Should we fix this in all applicable archetypes, and not just this one?
> It's in the quickstart as well, and probably others.
>
> /Anders
>
>
> On Wed, Nov 28, 2012 at 9:44 AM, Olivier Lamy  wrote:
>
>> ok I will re spin the release due to this old blocker issue :P
>>
>> 2012/11/27 Ansgar Konermann :
>> > Please remove it.
>> >
>> > I've seen it slipping into way too many poms of corporate projects, just
>> to
>> > add more noise to the poms and give maven a bad name for "being so hard
>> to
>> > understand".
>> >
>> > So it as soon as possible.
>> >
>> > TIA + BR
>> >
>> > Ansgar
>> > Am 27.11.2012 21:46 schrieb "Olivier Lamy" :
>> >
>> >> 2012/11/27 Robert Scholte :
>> >> > Hi Olivier,
>> >> >
>> >> > looks like a very nice and useful archetype.
>> >> > the configuration of the m-invoker-p could be smaller, since it
>> includes
>> >> > some defaults.
>> >> >
>> >> > There's only one thing which always surprises me: why is the url
>> filled
>> >> with
>> >> > our site?
>> >> marketing ? :-)
>> >> more seriously I have no idea about the history.
>> >> perso I don't have any trouble with that.
>> >> Folks can remove that (and must if they deploy a web site)
>> >> > I've seen a lot of projects started with archetypes and they all keep
>> >> this
>> >> > url untouched.
>> >> >
>> >> > I'd prefer to remove it, since it's almost never pointing to the
>> >> > project-page.
>> >> >
>> >> > -Robert
>> >> >
>> >> >
>> >> > Op Tue, 27 Nov 2012 00:54:58 +0100 schreef Olivier Lamy <
>> >> ol...@apache.org>:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> I'd like to release the archetype for maven plugin.
>> >> >> The goal is to have an archetype which generate project using new
>> mojo
>> >> >> annotations (and a sample to run maven-invoker-plugin)
>> >> >> We fixed 2 issues:
>> >> >> http://jira.codehaus.org/browse/MARCHETYPES/fixforversion/18708
>> >> >>
>> >> >> Staging repository:
>> >> >> https://repository.apache.org/content/repositories/maven-080/
>> >> >>
>> >> >> To test it:
>> >> >> mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes
>> >> >> -DarchetypeArtifactId=maven-archetype-plugin -DarchetypeVersion=1.2
>> >> >>
>> >> >> -DarchetypeRepository=
>> >> https://repository.apache.org/content/repositories/maven-080/
>> >> >>
>> >> >>
>> >> >> Vote open for 72 hours.
>> >> >>
>> >> >> [ ] +1
>> >> >> [ ] +0
>> >> >> [ ] -1
>> >> >>
>> >> >>
>> >> >> Thanks,
>> >> >> --
>> >> >> Olivier Lamy
>> >> >> Talend: http://coders.talend.com
>> >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >> >>
>> >> >> -
>> >> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> >> For additional commands, e-mail: dev-h...@maven.apache.org
>> >> >
>> >> >
>> >> > -
>> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Olivier Lamy
>> >> Talend: http://coders.talend.com
>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: dev-h...@maven.apache.org
>> >>
>> >>
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Arnaud Héritier
scm infos will have to be updated to reference git otherwise the
buildnumber plugin will try to extract some svn data from the local copy.


On Wed, Nov 28, 2012 at 10:12 AM, Stadelmann Josef <
josef.stadelm...@axa-winterthur.ch> wrote:

> after a
> $ git clone https://git-wip-us.apache.org/repos/asf/maven.git
> I got some mvn install
> build error. see attachment
> what can I do?
> Josef
>
>
>
> -Ursprüngliche Nachricht-
> Von: Arnaud Héritier [mailto:aherit...@gmail.com]
> Gesendet: Mittwoch, 28. November 2012 09:34
> An: Maven Developers List
> Betreff: Re: maven-3 and core-integration-testing git migration, needs
> verification
>
> But after the migration we remove them from SVN ?
> Perhaps with just a README to let people where it was moved ?
> Otherwise it will be really confusing and source of errors. No ?
>
>
> On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold <
> kristian.rosenv...@gmail.com> wrote:
>
> > SVN is read only while we test, this is standard procedure for
> migrations.
> >
> > (So if you *must* work on core in the next 24 hours, github is the
> > place to do it ;)
> >
> > Kristian
> >
> >
> >
> > 2012/11/28 Anders Hammar :
> > > Will the svn repo go read only once we switch, to prevent mistakes?
> > >
> > > /Anders
> > >
> > >
> > > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
> > > kristian.rosenv...@gmail.com> wrote:
> > >
> > >> The repos are located at:
> > >>
> > >> https://git-wip-us.apache.org/repos/asf/maven.git
> > >> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.g
> > >> it
> > >>
> > >>
> > >> Please "test" them, unless anyone has any objections they will
> > >> become r/w 24 hours from now.
> > >>
> > >>
> > >> The "3.1.0" tag is in the git repo, so I suppose this does not
> > >> affect the release unless we have to respin.
> > >>
> > >>
> > >> Kristian
> > >>
> > >> ---
> > >> -- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For
> > >> additional commands, e-mail: dev-h...@maven.apache.org
> > >>
> > >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For
> > additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
>
> --
> -
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aherit...@gmail.com
> Twitter/Skype : aheritier
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
-
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aherit...@gmail.com
Twitter/Skype : aheritier


Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 2)

2012-11-28 Thread Anders Hammar
-0

The created sample IT has a few minor issues IMO. I've fixed this in
r1414609. Your call if you have the energy to re-spin for this or leave it
to the next release.

/Anders


On Wed, Nov 28, 2012 at 9:54 AM, Olivier Lamy  wrote:

> Hi,
>
> I'd like to release the archetype for maven plugin.
> The goal is to have an archetype which generate project using new mojo
> annotations (and a sample to run maven-invoker-plugin)
> We fixed 2 issues:
> http://jira.codehaus.org/browse/MARCHETYPES/fixforversion/18708
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-089/
>
> To test it:
> mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes
> -DarchetypeArtifactId=maven-archetype-plugin -DarchetypeVersion=1.2
> -DarchetypeRepository=
> https://repository.apache.org/content/repositories/maven-089/
>
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> Thanks,
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 2)

2012-11-28 Thread Olivier Lamy
2012/11/28 Anders Hammar :
> -0
>
> The created sample IT has a few minor issues IMO. I've fixed this in
> r1414609. Your call if you have the energy to re-spin for this or leave it
> to the next release.
I will respin again as this one sucks !!.
As doesn't follow good conventions (archetype must be good samples !!)

Thanks for review and reporting that !!

so vote cancelled :-)

>
> /Anders
>
>
> On Wed, Nov 28, 2012 at 9:54 AM, Olivier Lamy  wrote:
>
>> Hi,
>>
>> I'd like to release the archetype for maven plugin.
>> The goal is to have an archetype which generate project using new mojo
>> annotations (and a sample to run maven-invoker-plugin)
>> We fixed 2 issues:
>> http://jira.codehaus.org/browse/MARCHETYPES/fixforversion/18708
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/maven-089/
>>
>> To test it:
>> mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes
>> -DarchetypeArtifactId=maven-archetype-plugin -DarchetypeVersion=1.2
>> -DarchetypeRepository=
>> https://repository.apache.org/content/repositories/maven-089/
>>
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>>
>> Thanks,
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>



--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 3)

2012-11-28 Thread Olivier Lamy
Hi,

I'd like to release the archetype for maven plugin.
The goal is to have an archetype which generate project using new mojo
annotations (and a sample to run maven-invoker-plugin)
We fixed 2 issues:
http://jira.codehaus.org/browse/MARCHETYPES/fixforversion/18708

Staging repository:
https://repository.apache.org/content/repositories/maven-090/

To test it:
mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes
-DarchetypeArtifactId=maven-archetype-plugin -DarchetypeVersion=1.2
-DarchetypeRepository=https://repository.apache.org/content/repositories/maven-090/


Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


Thanks,
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



AW: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Stadelmann Josef
in the maven/pom.xml the following is found
  

scm:svn:http://svn.apache.org/repos/asf/maven/maven-3/trunk

scm:svn:https://svn.apache.org/repos/asf/maven/maven-3/trunk
http://svn.apache.org/viewvc/maven/maven-3/trunk
  

I changed this to
  
  
scm:git:https//git-wip-us.apache.org/repos/asf/maven.git
  
scm:git:https//git-wip-us.apache.org/repos/asf/maven.git
  http://svn.apache.org/viewvc/maven/maven-3/trunk 
  
and got the build error below.

so what is the proper update to reference via git this maven.git project to 
build the project properly?
OR
Do I hunting a something which is just suppoed to work but does not yet work?
Josef


[buildnumber:create]
Storing buildNumber: NON-CANONICAL_2012-11-28_11-11_C770817 at timestamp: 
1354097462927
28.11.2012 11:11:02 org.sonatype.guice.bean.reflect.Logs$JULSink warn
WARNUNG: Error injecting: 
org.apache.maven.scm.provider.svn.svnjava.SvnJavaScmProvider
java.lang.NoClassDefFoundError: org/tmatesoft/svn/core/SVNException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getDeclaredConstructors(Class.java:1836)
at 
com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245)
at 
com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:98)
at 
com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:629)
at 
com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:831)
at 
com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:758)
at 
com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:255)
at 
com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:204)
at 
com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:954)
at 
com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:987)
at 
com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:950)
at 
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1000)
at 
org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:45)
at 
com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:84)
at 
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:52)
at 
com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
at 
org.sonatype.guice.plexus.lifecycles.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:138)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:108)
at 
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
at 
com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
at 
com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45)
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at 
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1018)
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:59)
at 
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at 
com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
at 
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
at 
org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:83)
at 
org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:49)
at java.util.AbstractMap.get(AbstractMap.java:165)
at 
org.apache.maven.scm.manager.AbstractScmManager.getProviderByType(AbstractScmManager.java:136)
at 
org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:190)
at 
org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:768)
at org.codehaus.mojo.build.CreateMojo.getScmBranch(CreateMojo.java:619)
at org.codehaus.mojo.build.CreateMojo.execute(CreateMojo.java:464)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginMan

Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 3)

2012-11-28 Thread Anders Hammar
Testing I now noticed this output:

[WARNING]

Goal prefix is specified as: 'archtst-maven-plugin'. Maven currently
expects it to be 'archtst'.

I never configure goalPrefix, do we need that? As it is now, using the
artifactId isn't really correct.

/Anders

On Wed, Nov 28, 2012 at 11:03 AM, Olivier Lamy  wrote:

> -DarchetypeRepository=
> https://repository.apache.org/content/repositories/maven-090/
>


Re: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Kristian Rosenvold
It builds fine here, with or without pom change

Kristian


2012/11/28 Stadelmann Josef 
> in the maven/pom.xml the following is found
>   
> 
> scm:svn:http://svn.apache.org/repos/asf/maven/maven-3/trunk
> 
> scm:svn:https://svn.apache.org/repos/asf/maven/maven-3/trunk
> http://svn.apache.org/viewvc/maven/maven-3/trunk
>   
>
> I changed this to
>   
>   
> scm:git:https//git-wip-us.apache.org/repos/asf/maven.git
>   
> scm:git:https//git-wip-us.apache.org/repos/asf/maven.git
>   http://svn.apache.org/viewvc/maven/maven-3/trunk
>   
> and got the build error below.
>
> so what is the proper update to reference via git this maven.git project to 
> build the project properly?
> OR
> Do I hunting a something which is just suppoed to work but does not yet work?
> Josef
>
>
> [buildnumber:create]
> Storing buildNumber: NON-CANONICAL_2012-11-28_11-11_C770817 at timestamp: 
> 1354097462927
> 28.11.2012 11:11:02 org.sonatype.guice.bean.reflect.Logs$JULSink warn
> WARNUNG: Error injecting: 
> org.apache.maven.scm.provider.svn.svnjava.SvnJavaScmProvider
> java.lang.NoClassDefFoundError: org/tmatesoft/svn/core/SVNException
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
> at java.lang.Class.getDeclaredConstructors(Class.java:1836)
> at 
> com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245)
> at 
> com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:98)
> at 
> com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:629)
> at 
> com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:831)
> at 
> com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:758)
> at 
> com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:255)
> at 
> com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:204)
> at 
> com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:954)
> at 
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:987)
> at 
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:950)
> at 
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1000)
> at 
> org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:45)
> at 
> com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:84)
> at 
> com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:52)
> at 
> com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at 
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
> at 
> org.sonatype.guice.plexus.lifecycles.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:138)
> at 
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:108)
> at 
> com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
> at 
> com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at 
> com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45)
> at 
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at 
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1018)
> at 
> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> at 
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
> at 
> com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
> at 
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
> at 
> com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
> at 
> org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:83)
> at 
> org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:49)
> at java.util.AbstractMap.get(AbstractMap.java:165)
> at 
> org.apache.maven.scm.manager.AbstractScmManager.getProviderByType(AbstractScmManager.java:136)
> at 
> org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:190)
> at 
> org.codehaus.mojo.build.CreateMojo

Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2

2012-11-28 Thread Brett Porter
What about making it an archetype parameter? e.g. http://svn.apache.org/r1414644

Would be nice to be optional, but don't think the archetype supports that in 
its manifest.

- Brett

On 28/11/2012, at 8:07 PM, Olivier Lamy  wrote:

> https://svn.apache.org/r1414409
> then
> https://svn.apache.org/r1414421
> 

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter






-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



AW: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Stadelmann Josef
in short it builds OK now!
I've changed in my settings.xml .m2 to .m22, then have maven-3.0.5 build this 
maven-3 release.
The build went OK! Then I compared briefly the new .m22 with the old .m2 
repository. I merged the
new repository into my old .m2 repository and changed settings.xml back to 
refer to old .m2 repository
and did a $ mvn clean install; now all has built OK. I don't know, why and when 
and circumstances my .m2
repository got bad content. but will certainly do this more frequently when 
problems arise. Some of the
content may well have made it to my .m2/repository through the AXA Winterthur 
Sonatype Repo-Server.
Sorry for the inconvenience, but I still do not understand what you Kristian 
said regarding 
Josef


-Ursprüngliche Nachricht-
Von: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] Im 
Auftrag von Kristian Rosenvold
Gesendet: Mittwoch, 28. November 2012 12:57
An: Maven Developers List
Betreff: Re: maven-3 and core-integration-testing git migration, needs 
verification

It builds fine here, with or without pom change

Kristian


2012/11/28 Stadelmann Josef 
> in the maven/pom.xml the following is found
>   
> 
> scm:svn:http://svn.apache.org/repos/asf/maven/maven-3/trunk
> 
> scm:svn:https://svn.apache.org/repos/asf/maven/maven-3/trunk
> http://svn.apache.org/viewvc/maven/maven-3/trunk
>   
>
> I changed this to
>   
>   
> scm:git:https//git-wip-us.apache.org/repos/asf/maven.git
>   
> scm:git:https//git-wip-us.apache.org/repos/asf/maven.git
>   http://svn.apache.org/viewvc/maven/maven-3/trunk
>   
> and got the build error below.
>
> so what is the proper update to reference via git this maven.git project to 
> build the project properly?
> OR
> Do I hunting a something which is just suppoed to work but does not yet work?
> Josef
>
>
> [buildnumber:create]
> Storing buildNumber: NON-CANONICAL_2012-11-28_11-11_C770817 at 
> timestamp: 1354097462927
> 28.11.2012 11:11:02 org.sonatype.guice.bean.reflect.Logs$JULSink warn
> WARNUNG: Error injecting: 
> org.apache.maven.scm.provider.svn.svnjava.SvnJavaScmProvider
> java.lang.NoClassDefFoundError: org/tmatesoft/svn/core/SVNException
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
> at java.lang.Class.getDeclaredConstructors(Class.java:1836)
> at 
> com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245)
> at 
> com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:98)
> at 
> com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:629)
> at 
> com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:831)
> at 
> com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:758)
> at 
> com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:255)
> at 
> com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:204)
> at 
> com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:954)
> at 
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:987)
> at 
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:950)
> at 
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1000)
> at 
> org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:45)
> at 
> com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:84)
> at 
> com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:52)
> at 
> com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at 
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
> at 
> org.sonatype.guice.plexus.lifecycles.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:138)
> at 
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:108)
> at 
> com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
> at 
> com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at 
> com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45)
> at 
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at 
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1018)
> at 
> com.google.inject.internal.ProviderToInternalFa

Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2

2012-11-28 Thread Anders Hammar
I don't think we should have http://maven.apache.org as the default. People
go with defaults Maybe http://foo.bar.org? Or just skip it.

/Anders


On Wed, Nov 28, 2012 at 1:24 PM, Brett Porter  wrote:

> What about making it an archetype parameter? e.g.
> http://svn.apache.org/r1414644
>
> Would be nice to be optional, but don't think the archetype supports that
> in its manifest.
>
> - Brett
>
> On 28/11/2012, at 8:07 PM, Olivier Lamy  wrote:
>
> > https://svn.apache.org/r1414409
> > then
> > https://svn.apache.org/r1414421
> >
>
> --
> Brett Porter
> br...@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 3)

2012-11-28 Thread Olivier Lamy
Perso, I won't consider that as blocker.
Any other troubles ?



2012/11/28 Anders Hammar :
> Testing I now noticed this output:
>
> [WARNING]
>
> Goal prefix is specified as: 'archtst-maven-plugin'. Maven currently
> expects it to be 'archtst'.
>
> I never configure goalPrefix, do we need that? As it is now, using the
> artifactId isn't really correct.
>
> /Anders
>
> On Wed, Nov 28, 2012 at 11:03 AM, Olivier Lamy  wrote:
>
>> -DarchetypeRepository=
>> https://repository.apache.org/content/repositories/maven-090/
>>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 3)

2012-11-28 Thread Anders Hammar
Nope, I'm +1 with everything else. I'll file a ticket for the warning and
fix it.

/Anders


On Wed, Nov 28, 2012 at 1:59 PM, Olivier Lamy  wrote:

> Perso, I won't consider that as blocker.
> Any other troubles ?
>
>
>
> 2012/11/28 Anders Hammar :
> > Testing I now noticed this output:
> >
> > [WARNING]
> >
> > Goal prefix is specified as: 'archtst-maven-plugin'. Maven currently
> > expects it to be 'archtst'.
> >
> > I never configure goalPrefix, do we need that? As it is now, using the
> > artifactId isn't really correct.
> >
> > /Anders
> >
> > On Wed, Nov 28, 2012 at 11:03 AM, Olivier Lamy  wrote:
> >
> >> -DarchetypeRepository=
> >> https://repository.apache.org/content/repositories/maven-090/
> >>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2

2012-11-28 Thread Brett Porter

On 28/11/2012, at 11:51 PM, Anders Hammar  wrote:

> I don't think we should have http://maven.apache.org as the default. People
> go with defaults Maybe http://foo.bar.org? Or just skip it.

Right...
http://svn.apache.org/viewvc/maven/archetypes/branches/with-properties/maven-archetype-webapp/src/main/resources/META-INF/maven/archetype-metadata.xml?r1=1414644&r2=1414643&pathrev=1414644

(You may have been looking at archetype.properties - that's an IT, which I left 
with the previous value)

- Brett

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter






-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Igor Fedorenko

+1 (non binding). Tried nexus and m2e builds, both worked without
problems. Also checked that 3.1.0 can be used in m2e as external maven
installation.

--
Regards,
Igor

On 12-11-26 1:24 AM, Jason van Zyl wrote:

Hi,

Here is a link to Jira with 30 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967

Staging repo:
https://repository.apache.org/content/repositories/maven-073/

The distributable binaries and sources for testing can be found here:
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/

Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz

Staging site:
http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0

The documentation specifically for this release pertains to JSR330 and 
SLF4J-based logging:
http://maven.apache.org/maven-jsr330.html
http://maven.apache.org/maven-logging.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.

-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Tony Chemit
On Sun, 25 Nov 2012 22:24:00 -0800
Jason van Zyl  wrote:

+1 (nb)

Works fine on our projects (nuiton.org, chorem.org) and also on some codehaus 
mojo.

thanks,

tony.

> Hi,
> 
> Here is a link to Jira with 30 issues resolved:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-073/
> 
> The distributable binaries and sources for testing can be found here:
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
> 
> Specifically the zip, tarball, and source archives can be found here:
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
> 
> Staging site:
> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
> 
> The documentation specifically for this release pertains to JSR330 and 
> SLF4J-based logging:
> http://maven.apache.org/maven-jsr330.html
> http://maven.apache.org/maven-logging.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> Thanks,
> 
> Jason
> 
> --
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
> 
> People develop abstractions by generalizing from concrete examples.
> Every attempt to determine the correct abstraction on paper without
> actually developing a running system is doomed to failure. No one
> is that smart. A framework is a resuable design, so you develop it by
> looking at the things it is supposed to be a design of. The more examples
> you look at, the more general your framework will be.
> 
> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com
http://www.codelutin.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Arnaud Héritier
+0
I found no technical regression but I see really few interest in this
release for now.
It is a minor version (due to some technical changes like in 3.0) while
there are only few bug fixes and nothing new interesting for end users.
I'm not against bug fixes releases but in that case we may have tried to at
least include something more interesting for end users (like the colored
console from olamy's branch -
https://github.com/aheritier/maven-3/tree/log4j2 - or to fix some real
annoying issues like aether rejecting artifacts from the local repository
when we change the mirror id in settings or when a remote repo isn't
available anymore - like when you move artifacts betweens staging repos).
It's dead to justify this release in the name of the "release early,
release often strategy" after 11 months thus we may have waited more weeks
to have something more interesting.
Thus nothing against it, but nothing in favor of it and I find that sad for
end-users.

But anyway, thx for the release and to all people involved in it.

Cheers,

Arnaud


On Wed, Nov 28, 2012 at 3:32 PM, Tony Chemit  wrote:

> On Sun, 25 Nov 2012 22:24:00 -0800
> Jason van Zyl  wrote:
>
> +1 (nb)
>
> Works fine on our projects (nuiton.org, chorem.org) and also on some
> codehaus mojo.
>
> thanks,
>
> tony.
>
> > Hi,
> >
> > Here is a link to Jira with 30 issues resolved:
> >
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-073/
> >
> > The distributable binaries and sources for testing can be found here:
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
> >
> > Specifically the zip, tarball, and source archives can be found here:
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
> >
> > Staging site:
> > http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
> >
> > The documentation specifically for this release pertains to JSR330 and
> SLF4J-based logging:
> > http://maven.apache.org/maven-jsr330.html
> > http://maven.apache.org/maven-logging.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Thanks,
> >
> > Jason
> >
> > --
> > Jason van Zyl
> > Founder & CTO, Sonatype
> > Founder,  Apache Maven
> > http://twitter.com/jvanzyl
> > -
> >
> > People develop abstractions by generalizing from concrete examples.
> > Every attempt to determine the correct abstraction on paper without
> > actually developing a running system is doomed to failure. No one
> > is that smart. A framework is a resuable design, so you develop it by
> > looking at the things it is supposed to be a design of. The more examples
> > you look at, the more general your framework will be.
> >
> > -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
>
> --
> Tony Chemit
> 
> tél: +33 (0) 2 40 50 29 28
> email: che...@codelutin.com
> http://www.codelutin.com
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
-
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aherit...@gmail.com
Twitter/Skype : aheritier


Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Benson Margulies
+1 (binding)

On Wed, Nov 28, 2012 at 11:04 AM, Arnaud Héritier  wrote:
> +0
> I found no technical regression but I see really few interest in this
> release for now.
> It is a minor version (due to some technical changes like in 3.0) while
> there are only few bug fixes and nothing new interesting for end users.
> I'm not against bug fixes releases but in that case we may have tried to at
> least include something more interesting for end users (like the colored
> console from olamy's branch -
> https://github.com/aheritier/maven-3/tree/log4j2 - or to fix some real
> annoying issues like aether rejecting artifacts from the local repository
> when we change the mirror id in settings or when a remote repo isn't
> available anymore - like when you move artifacts betweens staging repos).
> It's dead to justify this release in the name of the "release early,
> release often strategy" after 11 months thus we may have waited more weeks
> to have something more interesting.
> Thus nothing against it, but nothing in favor of it and I find that sad for
> end-users.
>
> But anyway, thx for the release and to all people involved in it.
>
> Cheers,
>
> Arnaud
>
>
> On Wed, Nov 28, 2012 at 3:32 PM, Tony Chemit  wrote:
>
>> On Sun, 25 Nov 2012 22:24:00 -0800
>> Jason van Zyl  wrote:
>>
>> +1 (nb)
>>
>> Works fine on our projects (nuiton.org, chorem.org) and also on some
>> codehaus mojo.
>>
>> thanks,
>>
>> tony.
>>
>> > Hi,
>> >
>> > Here is a link to Jira with 30 issues resolved:
>> >
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/maven-073/
>> >
>> > The distributable binaries and sources for testing can be found here:
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>> >
>> > Specifically the zip, tarball, and source archives can be found here:
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>> >
>> > Staging site:
>> > http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>> >
>> > The documentation specifically for this release pertains to JSR330 and
>> SLF4J-based logging:
>> > http://maven.apache.org/maven-jsr330.html
>> > http://maven.apache.org/maven-logging.html
>> >
>> > Vote open for 72 hours.
>> >
>> > [ ] +1
>> > [ ] +0
>> > [ ] -1
>> >
>> > Thanks,
>> >
>> > Jason
>> >
>> > --
>> > Jason van Zyl
>> > Founder & CTO, Sonatype
>> > Founder,  Apache Maven
>> > http://twitter.com/jvanzyl
>> > -
>> >
>> > People develop abstractions by generalizing from concrete examples.
>> > Every attempt to determine the correct abstraction on paper without
>> > actually developing a running system is doomed to failure. No one
>> > is that smart. A framework is a resuable design, so you develop it by
>> > looking at the things it is supposed to be a design of. The more examples
>> > you look at, the more general your framework will be.
>> >
>> > -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>>
>>
>>
>> --
>> Tony Chemit
>> 
>> tél: +33 (0) 2 40 50 29 28
>> email: che...@codelutin.com
>> http://www.codelutin.com
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
> --
> -
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aherit...@gmail.com
> Twitter/Skype : aheritier

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Daniel Kulp

+1

I've tested this with a few projects and it seems to work.

I DON'T like that it updates the war plugin to 2.3 as that version has issues 
on the Mac related to setting up an awt Toolkit.   However, there is a simple 
workaround of locking the war version down to 2.2 in the project pom (which is 
something the project in question should have done anyway).   

Dan



> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:
> 
>> Hi,
>> 
>> Here is a link to Jira with 30 issues resolved:
>> 
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>> 
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-073/
>> 
>> The distributable binaries and sources for testing can be found here:
>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>> 
>> Specifically the zip, tarball, and source archives can be found here:
>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>> 
>> Staging site:
>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>> 
>> The documentation specifically for this release pertains to JSR330 and
>> SLF4J-based logging:
>> http://maven.apache.org/maven-jsr330.html
>> http://maven.apache.org/maven-logging.html
>> 
>> Vote open for 72 hours.
>> 
>> [ ] +1
>> [ ] +0
>> [ ] -1
>> 
>> Thanks,
>> 
>> Jason
>> 

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Jason van Zyl
Note that I wasn't in favour of calling this 3.1.x. There are no user facing 
features per se but it is an important release, I believe, architecturally.

I think it's more important to get the momentum back. We were once releasing 
every six weeks and getting that swing back gets us more features for users. 
But I would be leery of trying to jam in a bunch user features when we have 
lost that momentum. There are still 700 or so bugs in JIRA, we lost one of the 
most important testing facilities in the embedded ITs, and I believe the ITs 
setup is generally flaky. I don't believe it's wise to try to provide higher 
level visibility in the form of new features when we have some lower level 
problems. Not releasing for 11 months is rather emblematic of that.

I, at the very least, plan to try and push out two or three more releases on a 
6 week schedule.  With a primary focus on making the ITs run in less than a 
minute, by whatever means necessary and trying to drive the issue count down.

On Nov 28, 2012, at 11:04 AM, Arnaud Héritier  wrote:

> +0
> I found no technical regression but I see really few interest in this
> release for now.
> It is a minor version (due to some technical changes like in 3.0) while
> there are only few bug fixes and nothing new interesting for end users.
> I'm not against bug fixes releases but in that case we may have tried to at
> least include something more interesting for end users (like the colored
> console from olamy's branch -
> https://github.com/aheritier/maven-3/tree/log4j2 - or to fix some real
> annoying issues like aether rejecting artifacts from the local repository
> when we change the mirror id in settings or when a remote repo isn't
> available anymore - like when you move artifacts betweens staging repos).
> It's dead to justify this release in the name of the "release early,
> release often strategy" after 11 months thus we may have waited more weeks
> to have something more interesting.
> Thus nothing against it, but nothing in favor of it and I find that sad for
> end-users.
> 
> But anyway, thx for the release and to all people involved in it.
> 
> Cheers,
> 
> Arnaud
> 
> 
> On Wed, Nov 28, 2012 at 3:32 PM, Tony Chemit  wrote:
> 
>> On Sun, 25 Nov 2012 22:24:00 -0800
>> Jason van Zyl  wrote:
>> 
>> +1 (nb)
>> 
>> Works fine on our projects (nuiton.org, chorem.org) and also on some
>> codehaus mojo.
>> 
>> thanks,
>> 
>> tony.
>> 
>>> Hi,
>>> 
>>> Here is a link to Jira with 30 issues resolved:
>>> 
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>>> 
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-073/
>>> 
>>> The distributable binaries and sources for testing can be found here:
>>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>>> 
>>> Specifically the zip, tarball, and source archives can be found here:
>>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>>> 
>>> Staging site:
>>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>>> 
>>> The documentation specifically for this release pertains to JSR330 and
>> SLF4J-based logging:
>>> http://maven.apache.org/maven-jsr330.html
>>> http://maven.apache.org/maven-logging.html
>>> 
>>> Vote open for 72 hours.
>>> 
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
>>> --
>>> Jason van Zyl
>>> Founder & CTO, Sonatype
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> -
>>> 
>>> People develop abstractions by generalizing from concrete examples.
>>> Every attempt to determine the correct abstraction on paper without
>>> actually developing a running system is doomed to failure. No one
>>> is that smart. A framework is a resuable design, so you develop it by
>>> looking at the things it is supposed to be a design of. The more examples
>>> you look at, the more general your framework will be.
>>> 
>>> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>> 
>> 
>> 
>> 
>> --
>> Tony Chemit
>> 
>> tél: +33 (0) 2 40 50 29 28
>> email: che...@codelutin.com
>> http://www.codelutin.com
>> 
>> --

Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Jason van Zyl
Well, if you think that's going to catch people out then that's reason to 
change it and spin it again.

I think it might be smarter to release new versions of the plugins and wait a 
cycle to integrate it into a release. This is assuming that we have more 
frequent releases.

It's no bother to spin again so if the compiler and war plugins are causing 
problems that's pretty significant.

On Nov 28, 2012, at 11:33 AM, Daniel Kulp  wrote:

> 
> +1
> 
> I've tested this with a few projects and it seems to work.
> 
> I DON'T like that it updates the war plugin to 2.3 as that version has issues 
> on the Mac related to setting up an awt Toolkit.   However, there is a simple 
> workaround of locking the war version down to 2.2 in the project pom (which 
> is something the project in question should have done anyway).   
> 
> Dan
> 
> 
> 
>> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:
>> 
>>> Hi,
>>> 
>>> Here is a link to Jira with 30 issues resolved:
>>> 
>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>>> 
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-073/
>>> 
>>> The distributable binaries and sources for testing can be found here:
>>> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>>> 
>>> Specifically the zip, tarball, and source archives can be found here:
>>> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>>> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>>> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>>> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>>> 
>>> Staging site:
>>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>>> 
>>> The documentation specifically for this release pertains to JSR330 and
>>> SLF4J-based logging:
>>> http://maven.apache.org/maven-jsr330.html
>>> http://maven.apache.org/maven-logging.html
>>> 
>>> Vote open for 72 hours.
>>> 
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
> 
> -- 
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

Selfish deeds are the shortest path to self destruction.

 -- The Seven Samuari, Akira Kurosawa







Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Arnaud Héritier
there is an issue opened about it ?
I didn't find it.


On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp  wrote:

>
> +1
>
> I've tested this with a few projects and it seems to work.
>
> I DON'T like that it updates the war plugin to 2.3 as that version has
> issues on the Mac related to setting up an awt Toolkit.   However, there is
> a simple workaround of locking the war version down to 2.2 in the project
> pom (which is something the project in question should have done anyway).
>
> Dan
>
>
>
> > On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:
> >
> >> Hi,
> >>
> >> Here is a link to Jira with 30 issues resolved:
> >>
> >>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-073/
> >>
> >> The distributable binaries and sources for testing can be found here:
> >>
> >>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
> >>
> >> Specifically the zip, tarball, and source archives can be found here:
> >>
> >>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
> >>
> >>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
> >>
> >>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
> >>
> >>
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
> >>
> >> Staging site:
> >> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
> >>
> >> The documentation specifically for this release pertains to JSR330 and
> >> SLF4J-based logging:
> >> http://maven.apache.org/maven-jsr330.html
> >> http://maven.apache.org/maven-logging.html
> >>
> >> Vote open for 72 hours.
> >>
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1
> >>
> >> Thanks,
> >>
> >> Jason
> >>
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
-
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aherit...@gmail.com
Twitter/Skype : aheritier


Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Daniel Kulp

On Nov 28, 2012, at 11:46 AM, Arnaud Héritier  wrote:

> there is an issue opened about it ?
> I didn't find it.

No, Olivier and I spent a chunk of time yesterday on IRC trying to figure out 
what was going on.   Once we figured it out, he committed a fix before I could 
even login to JIRA.  :-)


r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1 line
back tp xstream 1.4.2 to avoid http://jira.codehaus.org/browse/XSTR-709


Dan


> 
> 
> On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp  wrote:
> 
>> 
>> +1
>> 
>> I've tested this with a few projects and it seems to work.
>> 
>> I DON'T like that it updates the war plugin to 2.3 as that version has
>> issues on the Mac related to setting up an awt Toolkit.   However, there is
>> a simple workaround of locking the war version down to 2.2 in the project
>> pom (which is something the project in question should have done anyway).
>> 
>> Dan
>> 
>> 
>> 
>>> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:
>>> 
 Hi,
 
 Here is a link to Jira with 30 issues resolved:
 
 
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
 
 Staging repo:
 https://repository.apache.org/content/repositories/maven-073/
 
 The distributable binaries and sources for testing can be found here:
 
 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
 
 Specifically the zip, tarball, and source archives can be found here:
 
 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
 
 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
 
 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
 
 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
 
 Staging site:
 http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
 
 The documentation specifically for this release pertains to JSR330 and
 SLF4J-based logging:
 http://maven.apache.org/maven-jsr330.html
 http://maven.apache.org/maven-logging.html
 
 Vote open for 72 hours.
 
 [ ] +1
 [ ] +0
 [ ] -1
 
 Thanks,
 
 Jason
 
>> 
>> --
>> Daniel Kulp
>> dk...@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>> 
>> 
> 
> 
> -- 
> -
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aherit...@gmail.com
> Twitter/Skype : aheritier

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Olivier Lamy
2012/11/28 Daniel Kulp :
>
> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier  wrote:
>
>> there is an issue opened about it ?
>> I didn't find it.
>
> No, Olivier and I spent a chunk of time yesterday on IRC trying to figure out 
> what was going on.   Once we figured it out, he committed a fix before I 
> could even login to JIRA.  :-)
>
my bad I missed the jira entry
done http://jira.codehaus.org/browse/MWAR-295
>
> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1 line
> back tp xstream 1.4.2 to avoid http://jira.codehaus.org/browse/XSTR-709
>
>
> Dan
>
>
>>
>>
>> On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp  wrote:
>>
>>>
>>> +1
>>>
>>> I've tested this with a few projects and it seems to work.
>>>
>>> I DON'T like that it updates the war plugin to 2.3 as that version has
>>> issues on the Mac related to setting up an awt Toolkit.   However, there is
>>> a simple workaround of locking the war version down to 2.2 in the project
>>> pom (which is something the project in question should have done anyway).
>>>
>>> Dan
>>>
>>>
>>>
 On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:

> Hi,
>
> Here is a link to Jira with 30 issues resolved:
>
>
>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-073/
>
> The distributable binaries and sources for testing can be found here:
>
>
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>
> Specifically the zip, tarball, and source archives can be found here:
>
>
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>
>
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>
>
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>
>
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>
> Staging site:
> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>
> The documentation specifically for this release pertains to JSR330 and
> SLF4J-based logging:
> http://maven.apache.org/maven-jsr330.html
> http://maven.apache.org/maven-logging.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Thanks,
>
> Jason
>
>>>
>>> --
>>> Daniel Kulp
>>> dk...@apache.org - http://dankulp.com/blog
>>> Talend Community Coder - http://coders.talend.com
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>>
>> --
>> -
>> Arnaud Héritier
>> 06-89-76-64-24
>> http://aheritier.net
>> Mail/GTalk: aherit...@gmail.com
>> Twitter/Skype : aheritier
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Jason van Zyl
But what version of the plugin are users going to get?

On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:

> 
> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier  wrote:
> 
>> there is an issue opened about it ?
>> I didn't find it.
> 
> No, Olivier and I spent a chunk of time yesterday on IRC trying to figure out 
> what was going on.   Once we figured it out, he committed a fix before I 
> could even login to JIRA.  :-)
> 
> 
> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1 line
> back tp xstream 1.4.2 to avoid http://jira.codehaus.org/browse/XSTR-709
> 
> 
> Dan
> 
> 
>> 
>> 
>> On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp  wrote:
>> 
>>> 
>>> +1
>>> 
>>> I've tested this with a few projects and it seems to work.
>>> 
>>> I DON'T like that it updates the war plugin to 2.3 as that version has
>>> issues on the Mac related to setting up an awt Toolkit.   However, there is
>>> a simple workaround of locking the war version down to 2.2 in the project
>>> pom (which is something the project in question should have done anyway).
>>> 
>>> Dan
>>> 
>>> 
>>> 
 On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:
 
> Hi,
> 
> Here is a link to Jira with 30 issues resolved:
> 
> 
>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-073/
> 
> The distributable binaries and sources for testing can be found here:
> 
> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
> 
> Specifically the zip, tarball, and source archives can be found here:
> 
> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
> 
> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
> 
> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
> 
> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
> 
> Staging site:
> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
> 
> The documentation specifically for this release pertains to JSR330 and
> SLF4J-based logging:
> http://maven.apache.org/maven-jsr330.html
> http://maven.apache.org/maven-logging.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> Thanks,
> 
> Jason
> 
>>> 
>>> --
>>> Daniel Kulp
>>> dk...@apache.org - http://dankulp.com/blog
>>> Talend Community Coder - http://coders.talend.com
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>> 
>>> 
>> 
>> 
>> -- 
>> -
>> Arnaud Héritier
>> 06-89-76-64-24
>> http://aheritier.net
>> Mail/GTalk: aherit...@gmail.com
>> Twitter/Skype : aheritier
> 
> -- 
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

I never make the mistake of arguing with people for whose opinions I have no 
respect.

-- Edward Gibbon







Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Daniel Kulp

On Nov 28, 2012, at 12:33 PM, Jason van Zyl  wrote:
> But what version of the plugin are users going to get?

If it's not locked down, they would get 2.3.  (maven 3.0.x users get 2.1.3 I 
think)


However, I want to be clear:

* The issue ONLY affects Mac users.  Other platforms are OK.

* The issue only affects users that use the war plugin.   

* There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4 is 
released).  

* Another work around: adding the -Djava.awt.headless=true flag to the 
MAVEN_OPTS.

* The issue does NOT affect the output of the war plugin.  The plugin does 
exactly what it's supposed to do and produces a proper war.


The only "problem" is the Java Icon that would appear on the Mac Dock for the 
duration of the build.   It doesn't affect the actual build at all.   

So basically, it affects a relatively small number of maven users, doesn't 
affect the actual build at all, and has a relatively easy workaround for people 
that are annoyed by it.


Dan



> On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:
> 
>> 
>> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier  wrote:
>> 
>>> there is an issue opened about it ?
>>> I didn't find it.
>> 
>> No, Olivier and I spent a chunk of time yesterday on IRC trying to figure 
>> out what was going on.   Once we figured it out, he committed a fix before I 
>> could even login to JIRA.  :-)
>> 
>> 
>> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1 line
>> back tp xstream 1.4.2 to avoid http://jira.codehaus.org/browse/XSTR-709
>> 
>> 
>> Dan
>> 
>> 
>>> 
>>> 
>>> On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp  wrote:
>>> 
 
 +1
 
 I've tested this with a few projects and it seems to work.
 
 I DON'T like that it updates the war plugin to 2.3 as that version has
 issues on the Mac related to setting up an awt Toolkit.   However, there is
 a simple workaround of locking the war version down to 2.2 in the project
 pom (which is something the project in question should have done anyway).
 
 Dan
 
 
 
> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:
> 
>> Hi,
>> 
>> Here is a link to Jira with 30 issues resolved:
>> 
>> 
 https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>> 
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-073/
>> 
>> The distributable binaries and sources for testing can be found here:
>> 
>> 
 https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>> 
>> Specifically the zip, tarball, and source archives can be found here:
>> 
>> 
 https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>> 
>> 
 https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>> 
>> 
 https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>> 
>> 
 https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>> 
>> Staging site:
>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>> 
>> The documentation specifically for this release pertains to JSR330 and
>> SLF4J-based logging:
>> http://maven.apache.org/maven-jsr330.html
>> http://maven.apache.org/maven-logging.html
>> 
>> Vote open for 72 hours.
>> 
>> [ ] +1
>> [ ] +0
>> [ ] -1
>> 
>> Thanks,
>> 
>> Jason
>> 
 
 --
 Daniel Kulp
 dk...@apache.org - http://dankulp.com/blog
 Talend Community Coder - http://coders.talend.com
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
>>> 
>>> 
>>> -- 
>>> -
>>> Arnaud Héritier
>>> 06-89-76-64-24
>>> http://aheritier.net
>>> Mail/GTalk: aherit...@gmail.com
>>> Twitter/Skype : aheritier
>> 
>> -- 
>> Daniel Kulp
>> dk...@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>> 
> 
> Thanks,
> 
> Jason
> 
> --
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
> 
> I never make the mistake of arguing with people for whose opinions I have no 
> respect.
> 
> -- Edward Gibbon
> 
> 
> 
> 
> 

-- 
Daniel Kulp
dk...@apache.org - 

Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Jason van Zyl
Even for that it's probably worth re-spinning. I think the math is pretty easy 
there. It will take me 30 minutes to fix and re-release versus potentially 
thousands of people spending 10-20 minutes. People on Macs using the default 
version of the WAR plugin is probably not a small number. Why even expose it.

On Nov 28, 2012, at 12:54 PM, Daniel Kulp  wrote:

> 
> On Nov 28, 2012, at 12:33 PM, Jason van Zyl  wrote:
>> But what version of the plugin are users going to get?
> 
> If it's not locked down, they would get 2.3.  (maven 3.0.x users get 2.1.3 I 
> think)
> 
> 
> However, I want to be clear:
> 
> * The issue ONLY affects Mac users.  Other platforms are OK.
> 
> * The issue only affects users that use the war plugin.   
> 
> * There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4 is 
> released).  
> 
> * Another work around: adding the -Djava.awt.headless=true flag to the 
> MAVEN_OPTS.
> 
> * The issue does NOT affect the output of the war plugin.  The plugin does 
> exactly what it's supposed to do and produces a proper war.
> 
> 
> The only "problem" is the Java Icon that would appear on the Mac Dock for the 
> duration of the build.   It doesn't affect the actual build at all.   
> 
> So basically, it affects a relatively small number of maven users, doesn't 
> affect the actual build at all, and has a relatively easy workaround for 
> people that are annoyed by it.
> 
> 
> Dan
> 
> 
> 
>> On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:
>> 
>>> 
>>> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier  wrote:
>>> 
 there is an issue opened about it ?
 I didn't find it.
>>> 
>>> No, Olivier and I spent a chunk of time yesterday on IRC trying to figure 
>>> out what was going on.   Once we figured it out, he committed a fix before 
>>> I could even login to JIRA.  :-)
>>> 
>>> 
>>> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1 line
>>> back tp xstream 1.4.2 to avoid http://jira.codehaus.org/browse/XSTR-709
>>> 
>>> 
>>> Dan
>>> 
>>> 
 
 
 On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp  wrote:
 
> 
> +1
> 
> I've tested this with a few projects and it seems to work.
> 
> I DON'T like that it updates the war plugin to 2.3 as that version has
> issues on the Mac related to setting up an awt Toolkit.   However, there 
> is
> a simple workaround of locking the war version down to 2.2 in the project
> pom (which is something the project in question should have done anyway).
> 
> Dan
> 
> 
> 
>> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:
>> 
>>> Hi,
>>> 
>>> Here is a link to Jira with 30 issues resolved:
>>> 
>>> 
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>>> 
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-073/
>>> 
>>> The distributable binaries and sources for testing can be found here:
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>>> 
>>> Specifically the zip, tarball, and source archives can be found here:
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>>> 
>>> Staging site:
>>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>>> 
>>> The documentation specifically for this release pertains to JSR330 and
>>> SLF4J-based logging:
>>> http://maven.apache.org/maven-jsr330.html
>>> http://maven.apache.org/maven-logging.html
>>> 
>>> Vote open for 72 hours.
>>> 
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
> 
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 
 
 
 -- 
 -
 Arnaud Héritier
 06-89-76-64-24
 http://aheritier.net
 Mail/GTalk: aherit...@gmail.com
 Twitter/Skype : aheritier
>>> 
>>> -- 
>>> Daniel Kulp
>>> dk...@apache.org - http://dankulp.com/blog
>>> Talend Community Coder - http://coders.talend.com
>>> 
>>> 
>>> -

Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Robert Scholte
I agree with Arnaud: I'm still having trouble with a 3.1 due to the small  
number of really impressive changes, but the majority has decided to make  
it 3.1 [1]


-Robert

[1] http://markmail.org/message/7rvio4c5addzkmo4

Op Wed, 28 Nov 2012 17:35:02 +0100 schreef Jason van Zyl :

Note that I wasn't in favour of calling this 3.1.x. There are no user  
facing features per se but it is an important release, I believe,  
architecturally.


I think it's more important to get the momentum back. We were once  
releasing every six weeks and getting that swing back gets us more  
features for users. But I would be leery of trying to jam in a bunch  
user features when we have lost that momentum. There are still 700 or so  
bugs in JIRA, we lost one of the most important testing facilities in  
the embedded ITs, and I believe the ITs setup is generally flaky. I  
don't believe it's wise to try to provide higher level visibility in the  
form of new features when we have some lower level problems. Not  
releasing for 11 months is rather emblematic of that.


I, at the very least, plan to try and push out two or three more  
releases on a 6 week schedule.  With a primary focus on making the ITs  
run in less than a minute, by whatever means necessary and trying to  
drive the issue count down.


On Nov 28, 2012, at 11:04 AM, Arnaud Héritier   
wrote:



+0
I found no technical regression but I see really few interest in this
release for now.
It is a minor version (due to some technical changes like in 3.0) while
there are only few bug fixes and nothing new interesting for end users.
I'm not against bug fixes releases but in that case we may have tried  
to at

least include something more interesting for end users (like the colored
console from olamy's branch -
https://github.com/aheritier/maven-3/tree/log4j2 - or to fix some real
annoying issues like aether rejecting artifacts from the local  
repository

when we change the mirror id in settings or when a remote repo isn't
available anymore - like when you move artifacts betweens staging  
repos).

It's dead to justify this release in the name of the "release early,
release often strategy" after 11 months thus we may have waited more  
weeks

to have something more interesting.
Thus nothing against it, but nothing in favor of it and I find that sad  
for

end-users.

But anyway, thx for the release and to all people involved in it.

Cheers,

Arnaud


On Wed, Nov 28, 2012 at 3:32 PM, Tony Chemit   
wrote:



On Sun, 25 Nov 2012 22:24:00 -0800
Jason van Zyl  wrote:

+1 (nb)

Works fine on our projects (nuiton.org, chorem.org) and also on some
codehaus mojo.

thanks,

tony.


Hi,

Here is a link to Jira with 30 issues resolved:


https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967


Staging repo:
https://repository.apache.org/content/repositories/maven-073/

The distributable binaries and sources for testing can be found here:


https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/


Specifically the zip, tarball, and source archives can be found here:


https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip



https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz



https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip



https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz


Staging site:
http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0

The documentation specifically for this release pertains to JSR330 and

SLF4J-based logging:

http://maven.apache.org/maven-jsr330.html
http://maven.apache.org/maven-logging.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more  
examples

you look at, the more general your framework will be.

-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org





--
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com
http://www.codelutin.com

-

Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Mark Derricutt
I'd hazard a guess and say that this might actually be a rather large 
proportion of users.

If we're rolling new things, I'd prefer to see this rolled as a default since 
we're changing said default.

On 29/11/2012, at 6:54 AM, Daniel Kulp  wrote:

> * The issue ONLY affects Mac users.  Other platforms are OK.
> 
> * The issue only affects users that use the war plugin.   



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Arnaud Héritier
+1 with Jason to redo it.
What do we do ? Excepted this bug the 2.3 was interesting to have for
performances improvements and few bug fixes. Could we release a 2.3.1 and
then/or in // re-release 3.1.0 ?
WDYT ?


On Wed, Nov 28, 2012 at 7:17 PM, Jason van Zyl  wrote:

> Even for that it's probably worth re-spinning. I think the math is pretty
> easy there. It will take me 30 minutes to fix and re-release versus
> potentially thousands of people spending 10-20 minutes. People on Macs
> using the default version of the WAR plugin is probably not a small number.
> Why even expose it.
>
> On Nov 28, 2012, at 12:54 PM, Daniel Kulp  wrote:
>
> >
> > On Nov 28, 2012, at 12:33 PM, Jason van Zyl  wrote:
> >> But what version of the plugin are users going to get?
> >
> > If it's not locked down, they would get 2.3.  (maven 3.0.x users get
> 2.1.3 I think)
> >
> >
> > However, I want to be clear:
> >
> > * The issue ONLY affects Mac users.  Other platforms are OK.
> >
> > * The issue only affects users that use the war plugin.
> >
> > * There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4
> is released).
> >
> > * Another work around: adding the -Djava.awt.headless=true flag to the
> MAVEN_OPTS.
> >
> > * The issue does NOT affect the output of the war plugin.  The plugin
> does exactly what it's supposed to do and produces a proper war.
> >
> >
> > The only "problem" is the Java Icon that would appear on the Mac Dock
> for the duration of the build.   It doesn't affect the actual build at all.
> >
> > So basically, it affects a relatively small number of maven users,
> doesn't affect the actual build at all, and has a relatively easy
> workaround for people that are annoyed by it.
> >
> >
> > Dan
> >
> >
> >
> >> On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:
> >>
> >>>
> >>> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier 
> wrote:
> >>>
>  there is an issue opened about it ?
>  I didn't find it.
> >>>
> >>> No, Olivier and I spent a chunk of time yesterday on IRC trying to
> figure out what was going on.   Once we figured it out, he committed a fix
> before I could even login to JIRA.  :-)
> >>>
> >>>
> >>> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1
> line
> >>> back tp xstream 1.4.2 to avoid
> http://jira.codehaus.org/browse/XSTR-709
> >>>
> >>>
> >>> Dan
> >>>
> >>>
> 
> 
>  On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp 
> wrote:
> 
> >
> > +1
> >
> > I've tested this with a few projects and it seems to work.
> >
> > I DON'T like that it updates the war plugin to 2.3 as that version
> has
> > issues on the Mac related to setting up an awt Toolkit.   However,
> there is
> > a simple workaround of locking the war version down to 2.2 in the
> project
> > pom (which is something the project in question should have done
> anyway).
> >
> > Dan
> >
> >
> >
> >> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl 
> wrote:
> >>
> >>> Hi,
> >>>
> >>> Here is a link to Jira with 30 issues resolved:
> >>>
> >>>
> >
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
> >>>
> >>> Staging repo:
> >>> https://repository.apache.org/content/repositories/maven-073/
> >>>
> >>> The distributable binaries and sources for testing can be found
> here:
> >>>
> >>>
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
> >>>
> >>> Specifically the zip, tarball, and source archives can be found
> here:
> >>>
> >>>
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
> >>>
> >>>
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
> >>>
> >>>
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
> >>>
> >>>
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
> >>>
> >>> Staging site:
> >>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
> >>>
> >>> The documentation specifically for this release pertains to JSR330
> and
> >>> SLF4J-based logging:
> >>> http://maven.apache.org/maven-jsr330.html
> >>> http://maven.apache.org/maven-logging.html
> >>>
> >>> Vote open for 72 hours.
> >>>
> >>> [ ] +1
> >>> [ ] +0
> >>> [ ] -1
> >>>
> >>> Thanks,
> >>>
> >>> Jason
> >>>
> >
> > --
> > Daniel Kulp
> > dk...@apache.org - http://dankulp.com/blog
> > Talend Community Coder - http://coders.talend.com
> >
> >
> > -
> > To unsubscribe, e-mail: dev

Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 3)

2012-11-28 Thread Anders Hammar
Hold on here, working on something else I actually checked the created
source for the generated touch mojo. Why does it say this:

@deprecated Don't use!

Also, should we really include the license header in the code of the
generated plugin? Not sure that's what people want.

/Anders


On Wed, Nov 28, 2012 at 2:32 PM, Anders Hammar  wrote:

> Nope, I'm +1 with everything else. I'll file a ticket for the warning and
> fix it.
>
> /Anders
>
>
>
> On Wed, Nov 28, 2012 at 1:59 PM, Olivier Lamy  wrote:
>
>> Perso, I won't consider that as blocker.
>> Any other troubles ?
>>
>>
>>
>> 2012/11/28 Anders Hammar :
>> > Testing I now noticed this output:
>> >
>> > [WARNING]
>> >
>> > Goal prefix is specified as: 'archtst-maven-plugin'. Maven currently
>> > expects it to be 'archtst'.
>> >
>> > I never configure goalPrefix, do we need that? As it is now, using the
>> > artifactId isn't really correct.
>> >
>> > /Anders
>> >
>> > On Wed, Nov 28, 2012 at 11:03 AM, Olivier Lamy 
>> wrote:
>> >
>> >> -DarchetypeRepository=
>> >> https://repository.apache.org/content/repositories/maven-090/
>> >>
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>


Versions in the MARCHETYPES JIRA project

2012-11-28 Thread Anders Hammar
I see we have different formats of the versions in the MARCHETYPES project
in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.

If I fix a ticket, what should I set the fix versions as? Are we going to
keep separate release flows for each component or are we going to release
them all together? I would say releasing them separately is a lot of
overhead work.

/Anders


Re: Versions in the MARCHETYPES JIRA project

2012-11-28 Thread Olivier Lamy
2012/11/28 Anders Hammar :
> I see we have different formats of the versions in the MARCHETYPES project
> in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.
5 is for parent pom
1.1 was probably when all archetypes were released at the same time.
imho the format maven-archetype-plugin-1.2 is what we have to use now.
>
> If I fix a ticket, what should I set the fix versions as? Are we going to
> keep separate release flows for each component or are we going to release
> them all together? I would say releasing them separately is a lot of
> overhead work.
>
> /Anders



--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Versions in the MARCHETYPES JIRA project

2012-11-28 Thread Anders Hammar
Ok, separate releases it is then. I'll do some cleaning in the JIRA project.

/Anders


On Wed, Nov 28, 2012 at 9:12 PM, Olivier Lamy  wrote:

> 2012/11/28 Anders Hammar :
> > I see we have different formats of the versions in the MARCHETYPES
> project
> > in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.
> 5 is for parent pom
> 1.1 was probably when all archetypes were released at the same time.
> imho the format maven-archetype-plugin-1.2 is what we have to use now.
> >
> > If I fix a ticket, what should I set the fix versions as? Are we going to
> > keep separate release flows for each component or are we going to release
> > them all together? I would say releasing them separately is a lot of
> > overhead work.
> >
> > /Anders
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: Versions in the MARCHETYPES JIRA project

2012-11-28 Thread Anders Hammar
Btw, anyone against changing "5" to "parent-5" to remove some confusion
with the older "1.1" etc?

/Anders


On Wed, Nov 28, 2012 at 9:14 PM, Anders Hammar  wrote:

> Ok, separate releases it is then. I'll do some cleaning in the JIRA
> project.
>
> /Anders
>
>
>
> On Wed, Nov 28, 2012 at 9:12 PM, Olivier Lamy  wrote:
>
>> 2012/11/28 Anders Hammar :
>> > I see we have different formats of the versions in the MARCHETYPES
>> project
>> > in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.
>> 5 is for parent pom
>> 1.1 was probably when all archetypes were released at the same time.
>> imho the format maven-archetype-plugin-1.2 is what we have to use now.
>> >
>> > If I fix a ticket, what should I set the fix versions as? Are we going
>> to
>> > keep separate release flows for each component or are we going to
>> release
>> > them all together? I would say releasing them separately is a lot of
>> > overhead work.
>> >
>> > /Anders
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>


Re: Versions in the MARCHETYPES JIRA project

2012-11-28 Thread Anders Hammar
> Ok, separate releases it is then. I'll do some cleaning in the JIRA
> project.
>

Eh, I spoke too soon. There's quite a mess in that project. The "5" version
is not just for the parent but other things as well.
I'm thinking we just remove the 1.1, 1.2, and 5 versions and do it right
from here. There is currently only 14 closed ticket, and those that will
loose a fix version could get back-tracked if it would  turn out to be of
interest (which I doubt). Anyone against?


>
> /Anders
>
>
>
> On Wed, Nov 28, 2012 at 9:12 PM, Olivier Lamy  wrote:
>
>> 2012/11/28 Anders Hammar :
>> > I see we have different formats of the versions in the MARCHETYPES
>> project
>> > in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.
>> 5 is for parent pom
>> 1.1 was probably when all archetypes were released at the same time.
>> imho the format maven-archetype-plugin-1.2 is what we have to use now.
>> >
>> > If I fix a ticket, what should I set the fix versions as? Are we going
>> to
>> > keep separate release flows for each component or are we going to
>> release
>> > them all together? I would say releasing them separately is a lot of
>> > overhead work.
>> >
>> > /Anders
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>


Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 3)

2012-11-28 Thread Olivier Lamy
2012/11/28 Anders Hammar :
> Hold on here, working on something else I actually checked the created
> source for the generated touch mojo. Why does it say this:
>
> @deprecated Don't use!
oh I probably copy/paste the mojo code and missed to remove that
BTW as it's a mojo sample generated by the archetype users can/must
remove it :-)
>
> Also, should we really include the license header in the code of the
> generated plugin? Not sure that's what people want.

See http://jira.codehaus.org/browse/MARCHETYPES-38 (I agree our
sources must have asl header)
But I agree too to not generate sources with asf headers as some users
can use something else.
see the solution here: http://svn.apache.org/r1414907


>
> /Anders
>
>
> On Wed, Nov 28, 2012 at 2:32 PM, Anders Hammar  wrote:
>
>> Nope, I'm +1 with everything else. I'll file a ticket for the warning and
>> fix it.
>>
>> /Anders
>>
>>
>>
>> On Wed, Nov 28, 2012 at 1:59 PM, Olivier Lamy  wrote:
>>
>>> Perso, I won't consider that as blocker.
>>> Any other troubles ?
>>>
>>>
>>>
>>> 2012/11/28 Anders Hammar :
>>> > Testing I now noticed this output:
>>> >
>>> > [WARNING]
>>> >
>>> > Goal prefix is specified as: 'archtst-maven-plugin'. Maven currently
>>> > expects it to be 'archtst'.
>>> >
>>> > I never configure goalPrefix, do we need that? As it is now, using the
>>> > artifactId isn't really correct.
>>> >
>>> > /Anders
>>> >
>>> > On Wed, Nov 28, 2012 at 11:03 AM, Olivier Lamy 
>>> wrote:
>>> >
>>> >> -DarchetypeRepository=
>>> >> https://repository.apache.org/content/repositories/maven-090/
>>> >>
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Benson Margulies
It's an extremely minor annoyance, writing as one of the victims.
Please don't make Jason re-roll. I have better idea for the use of his
time.

On Wed, Nov 28, 2012 at 1:40 PM, Arnaud Héritier  wrote:
> +1 with Jason to redo it.
> What do we do ? Excepted this bug the 2.3 was interesting to have for
> performances improvements and few bug fixes. Could we release a 2.3.1 and
> then/or in // re-release 3.1.0 ?
> WDYT ?
>
>
> On Wed, Nov 28, 2012 at 7:17 PM, Jason van Zyl  wrote:
>
>> Even for that it's probably worth re-spinning. I think the math is pretty
>> easy there. It will take me 30 minutes to fix and re-release versus
>> potentially thousands of people spending 10-20 minutes. People on Macs
>> using the default version of the WAR plugin is probably not a small number.
>> Why even expose it.
>>
>> On Nov 28, 2012, at 12:54 PM, Daniel Kulp  wrote:
>>
>> >
>> > On Nov 28, 2012, at 12:33 PM, Jason van Zyl  wrote:
>> >> But what version of the plugin are users going to get?
>> >
>> > If it's not locked down, they would get 2.3.  (maven 3.0.x users get
>> 2.1.3 I think)
>> >
>> >
>> > However, I want to be clear:
>> >
>> > * The issue ONLY affects Mac users.  Other platforms are OK.
>> >
>> > * The issue only affects users that use the war plugin.
>> >
>> > * There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4
>> is released).
>> >
>> > * Another work around: adding the -Djava.awt.headless=true flag to the
>> MAVEN_OPTS.
>> >
>> > * The issue does NOT affect the output of the war plugin.  The plugin
>> does exactly what it's supposed to do and produces a proper war.
>> >
>> >
>> > The only "problem" is the Java Icon that would appear on the Mac Dock
>> for the duration of the build.   It doesn't affect the actual build at all.
>> >
>> > So basically, it affects a relatively small number of maven users,
>> doesn't affect the actual build at all, and has a relatively easy
>> workaround for people that are annoyed by it.
>> >
>> >
>> > Dan
>> >
>> >
>> >
>> >> On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:
>> >>
>> >>>
>> >>> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier 
>> wrote:
>> >>>
>>  there is an issue opened about it ?
>>  I didn't find it.
>> >>>
>> >>> No, Olivier and I spent a chunk of time yesterday on IRC trying to
>> figure out what was going on.   Once we figured it out, he committed a fix
>> before I could even login to JIRA.  :-)
>> >>>
>> >>>
>> >>> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1
>> line
>> >>> back tp xstream 1.4.2 to avoid
>> http://jira.codehaus.org/browse/XSTR-709
>> >>>
>> >>>
>> >>> Dan
>> >>>
>> >>>
>> 
>> 
>>  On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp 
>> wrote:
>> 
>> >
>> > +1
>> >
>> > I've tested this with a few projects and it seems to work.
>> >
>> > I DON'T like that it updates the war plugin to 2.3 as that version
>> has
>> > issues on the Mac related to setting up an awt Toolkit.   However,
>> there is
>> > a simple workaround of locking the war version down to 2.2 in the
>> project
>> > pom (which is something the project in question should have done
>> anyway).
>> >
>> > Dan
>> >
>> >
>> >
>> >> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl 
>> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> Here is a link to Jira with 30 issues resolved:
>> >>>
>> >>>
>> >
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>> >>>
>> >>> Staging repo:
>> >>> https://repository.apache.org/content/repositories/maven-073/
>> >>>
>> >>> The distributable binaries and sources for testing can be found
>> here:
>> >>>
>> >>>
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>> >>>
>> >>> Specifically the zip, tarball, and source archives can be found
>> here:
>> >>>
>> >>>
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>> >>>
>> >>>
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>> >>>
>> >>>
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>> >>>
>> >>>
>> >
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>> >>>
>> >>> Staging site:
>> >>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>> >>>
>> >>> The documentation specifically for this release pertains to JSR330
>> and
>> >>> SLF4J-based logging:
>> >>> http://maven.apache.org/maven-jsr330.html
>> >>> http://maven.apache.org/maven-logging.html
>> >>>
>> >>> Vote open for 72 hours.
>> >>>
>> >>> [ ] +1
>> >>> [ ] +0

Re: [VOTE] Maven 3.1.0

2012-11-28 Thread John Casey

+1

It appears to work fine on my largest builds here.

On 11/26/12 12:24 AM, Jason van Zyl wrote:

Hi,

Here is a link to Jira with 30 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967

Staging repo:
https://repository.apache.org/content/repositories/maven-073/

The distributable binaries and sources for testing can be found here:
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/

Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz

Staging site:
http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0

The documentation specifically for this release pertains to JSR330 and 
SLF4J-based logging:
http://maven.apache.org/maven-jsr330.html
http://maven.apache.org/maven-logging.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.

-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
GitHub - http://github.com/jdcasey

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Jason van Zyl
I honestly don't mind re-spinning. It's not a big deal. What about the compiler 
plugin?

jvz

On 2012-11-28, at 3:38 PM, Benson Margulies  wrote:

> It's an extremely minor annoyance, writing as one of the victims.
> Please don't make Jason re-roll. I have better idea for the use of his
> time.
> 
> On Wed, Nov 28, 2012 at 1:40 PM, Arnaud Héritier  wrote:
>> +1 with Jason to redo it.
>> What do we do ? Excepted this bug the 2.3 was interesting to have for
>> performances improvements and few bug fixes. Could we release a 2.3.1 and
>> then/or in // re-release 3.1.0 ?
>> WDYT ?
>> 
>> 
>> On Wed, Nov 28, 2012 at 7:17 PM, Jason van Zyl  wrote:
>> 
>>> Even for that it's probably worth re-spinning. I think the math is pretty
>>> easy there. It will take me 30 minutes to fix and re-release versus
>>> potentially thousands of people spending 10-20 minutes. People on Macs
>>> using the default version of the WAR plugin is probably not a small number.
>>> Why even expose it.
>>> 
>>> On Nov 28, 2012, at 12:54 PM, Daniel Kulp  wrote:
>>> 
 
 On Nov 28, 2012, at 12:33 PM, Jason van Zyl  wrote:
> But what version of the plugin are users going to get?
 
 If it's not locked down, they would get 2.3.  (maven 3.0.x users get
>>> 2.1.3 I think)
 
 
 However, I want to be clear:
 
 * The issue ONLY affects Mac users.  Other platforms are OK.
 
 * The issue only affects users that use the war plugin.
 
 * There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4
>>> is released).
 
 * Another work around: adding the -Djava.awt.headless=true flag to the
>>> MAVEN_OPTS.
 
 * The issue does NOT affect the output of the war plugin.  The plugin
>>> does exactly what it's supposed to do and produces a proper war.
 
 
 The only "problem" is the Java Icon that would appear on the Mac Dock
>>> for the duration of the build.   It doesn't affect the actual build at all.
 
 So basically, it affects a relatively small number of maven users,
>>> doesn't affect the actual build at all, and has a relatively easy
>>> workaround for people that are annoyed by it.
 
 
 Dan
 
 
 
> On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:
> 
>> 
>> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier 
>>> wrote:
>> 
>>> there is an issue opened about it ?
>>> I didn't find it.
>> 
>> No, Olivier and I spent a chunk of time yesterday on IRC trying to
>>> figure out what was going on.   Once we figured it out, he committed a fix
>>> before I could even login to JIRA.  :-)
>> 
>> 
>> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1
>>> line
>> back tp xstream 1.4.2 to avoid
>>> http://jira.codehaus.org/browse/XSTR-709
>> 
>> 
>> Dan
>> 
>> 
>>> 
>>> 
>>> On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp 
>>> wrote:
>>> 
 
 +1
 
 I've tested this with a few projects and it seems to work.
 
 I DON'T like that it updates the war plugin to 2.3 as that version
>>> has
 issues on the Mac related to setting up an awt Toolkit.   However,
>>> there is
 a simple workaround of locking the war version down to 2.2 in the
>>> project
 pom (which is something the project in question should have done
>>> anyway).
 
 Dan
 
 
 
> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl 
>>> wrote:
> 
>> Hi,
>> 
>> Here is a link to Jira with 30 issues resolved:
>> 
>> 
 
>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>> 
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-073/
>> 
>> The distributable binaries and sources for testing can be found
>>> here:
>> 
>> 
 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>> 
>> Specifically the zip, tarball, and source archives can be found
>>> here:
>> 
>> 
 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>> 
>> 
 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>> 
>> 
 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>> 
>> 
 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>> 
>> Staging site:
>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>> 
>> The documentation specifically for th

Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Dennis Lundberg
Hi

The compiler plugin is at 2.5.1 in the release. The 3.0 release was
deemed to be to new to be included as default in core.

On 2012-11-28 22:08, Jason van Zyl wrote:
> I honestly don't mind re-spinning. It's not a big deal. What about the 
> compiler plugin?
> 
> jvz
> 
> On 2012-11-28, at 3:38 PM, Benson Margulies  wrote:
> 
>> It's an extremely minor annoyance, writing as one of the victims.
>> Please don't make Jason re-roll. I have better idea for the use of his
>> time.
>>
>> On Wed, Nov 28, 2012 at 1:40 PM, Arnaud Héritier  wrote:
>>> +1 with Jason to redo it.
>>> What do we do ? Excepted this bug the 2.3 was interesting to have for
>>> performances improvements and few bug fixes. Could we release a 2.3.1 and
>>> then/or in // re-release 3.1.0 ?
>>> WDYT ?
>>>
>>>
>>> On Wed, Nov 28, 2012 at 7:17 PM, Jason van Zyl  wrote:
>>>
 Even for that it's probably worth re-spinning. I think the math is pretty
 easy there. It will take me 30 minutes to fix and re-release versus
 potentially thousands of people spending 10-20 minutes. People on Macs
 using the default version of the WAR plugin is probably not a small number.
 Why even expose it.

 On Nov 28, 2012, at 12:54 PM, Daniel Kulp  wrote:

>
> On Nov 28, 2012, at 12:33 PM, Jason van Zyl  wrote:
>> But what version of the plugin are users going to get?
>
> If it's not locked down, they would get 2.3.  (maven 3.0.x users get
 2.1.3 I think)
>
>
> However, I want to be clear:
>
> * The issue ONLY affects Mac users.  Other platforms are OK.
>
> * The issue only affects users that use the war plugin.
>
> * There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4
 is released).
>
> * Another work around: adding the -Djava.awt.headless=true flag to the
 MAVEN_OPTS.
>
> * The issue does NOT affect the output of the war plugin.  The plugin
 does exactly what it's supposed to do and produces a proper war.
>
>
> The only "problem" is the Java Icon that would appear on the Mac Dock
 for the duration of the build.   It doesn't affect the actual build at all.
>
> So basically, it affects a relatively small number of maven users,
 doesn't affect the actual build at all, and has a relatively easy
 workaround for people that are annoyed by it.
>
>
> Dan
>
>
>
>> On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:
>>
>>>
>>> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier 
 wrote:
>>>
 there is an issue opened about it ?
 I didn't find it.
>>>
>>> No, Olivier and I spent a chunk of time yesterday on IRC trying to
 figure out what was going on.   Once we figured it out, he committed a fix
 before I could even login to JIRA.  :-)
>>>
>>>
>>> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1
 line
>>> back tp xstream 1.4.2 to avoid
 http://jira.codehaus.org/browse/XSTR-709
>>>
>>>
>>> Dan
>>>
>>>


 On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp 
 wrote:

>
> +1
>
> I've tested this with a few projects and it seems to work.
>
> I DON'T like that it updates the war plugin to 2.3 as that version
 has
> issues on the Mac related to setting up an awt Toolkit.   However,
 there is
> a simple workaround of locking the war version down to 2.2 in the
 project
> pom (which is something the project in question should have done
 anyway).
>
> Dan
>
>
>
>> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl 
 wrote:
>>
>>> Hi,
>>>
>>> Here is a link to Jira with 30 issues resolved:
>>>
>>>
>
 https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-073/
>>>
>>> The distributable binaries and sources for testing can be found
 here:
>>>
>>>
>
 https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>>>
>>> Specifically the zip, tarball, and source archives can be found
 here:
>>>
>>>
>
 https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>>>
>>>
>
 https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>>>
>>>
>
 https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>>>
>>>
>
 https://repository.apache.org/c

Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 3)

2012-11-28 Thread Anders Hammar
> See http://jira.codehaus.org/browse/MARCHETYPES-38 (I agree our
> sources must have asl header)
> But I agree too to not generate sources with asf headers as some users
> can use something else.
> see the solution here: http://svn.apache.org/r1414907
>

The generated source in the quickstart archetype does not have any kind of
license header.

/Anders


>
>
> >
> > /Anders
> >
> >
> > On Wed, Nov 28, 2012 at 2:32 PM, Anders Hammar 
> wrote:
> >
> >> Nope, I'm +1 with everything else. I'll file a ticket for the warning
> and
> >> fix it.
> >>
> >> /Anders
> >>
> >>
> >>
> >> On Wed, Nov 28, 2012 at 1:59 PM, Olivier Lamy  wrote:
> >>
> >>> Perso, I won't consider that as blocker.
> >>> Any other troubles ?
> >>>
> >>>
> >>>
> >>> 2012/11/28 Anders Hammar :
> >>> > Testing I now noticed this output:
> >>> >
> >>> > [WARNING]
> >>> >
> >>> > Goal prefix is specified as: 'archtst-maven-plugin'. Maven currently
> >>> > expects it to be 'archtst'.
> >>> >
> >>> > I never configure goalPrefix, do we need that? As it is now, using
> the
> >>> > artifactId isn't really correct.
> >>> >
> >>> > /Anders
> >>> >
> >>> > On Wed, Nov 28, 2012 at 11:03 AM, Olivier Lamy 
> >>> wrote:
> >>> >
> >>> >> -DarchetypeRepository=
> >>> >> https://repository.apache.org/content/repositories/maven-090/
> >>> >>
> >>>
> >>>
> >>>
> >>> --
> >>> Olivier Lamy
> >>> Talend: http://coders.talend.com
> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: dev-h...@maven.apache.org
> >>>
> >>>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 3)

2012-11-28 Thread Olivier Lamy
2012/11/28 Anders Hammar :
>> See http://jira.codehaus.org/browse/MARCHETYPES-38 (I agree our
>> sources must have asl header)
>> But I agree too to not generate sources with asf headers as some users
>> can use something else.
>> see the solution here: http://svn.apache.org/r1414907
>>
>
> The generated source in the quickstart archetype does not have any kind of
> license header.
yup I have never said MARCHETYPES-38 was fixed :-)
>
> /Anders
>
>
>>
>>
>> >
>> > /Anders
>> >
>> >
>> > On Wed, Nov 28, 2012 at 2:32 PM, Anders Hammar 
>> wrote:
>> >
>> >> Nope, I'm +1 with everything else. I'll file a ticket for the warning
>> and
>> >> fix it.
>> >>
>> >> /Anders
>> >>
>> >>
>> >>
>> >> On Wed, Nov 28, 2012 at 1:59 PM, Olivier Lamy  wrote:
>> >>
>> >>> Perso, I won't consider that as blocker.
>> >>> Any other troubles ?
>> >>>
>> >>>
>> >>>
>> >>> 2012/11/28 Anders Hammar :
>> >>> > Testing I now noticed this output:
>> >>> >
>> >>> > [WARNING]
>> >>> >
>> >>> > Goal prefix is specified as: 'archtst-maven-plugin'. Maven currently
>> >>> > expects it to be 'archtst'.
>> >>> >
>> >>> > I never configure goalPrefix, do we need that? As it is now, using
>> the
>> >>> > artifactId isn't really correct.
>> >>> >
>> >>> > /Anders
>> >>> >
>> >>> > On Wed, Nov 28, 2012 at 11:03 AM, Olivier Lamy 
>> >>> wrote:
>> >>> >
>> >>> >> -DarchetypeRepository=
>> >>> >> https://repository.apache.org/content/repositories/maven-090/
>> >>> >>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Olivier Lamy
>> >>> Talend: http://coders.talend.com
>> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>
>> >>> -
>> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >>> For additional commands, e-mail: dev-h...@maven.apache.org
>> >>>
>> >>>
>> >>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>



--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven Archetypes Parent 5 and Maven Archetype Plugin 1.2 (take 3)

2012-11-28 Thread Benson Margulies
On Wed, Nov 28, 2012 at 4:41 PM, Olivier Lamy  wrote:
> 2012/11/28 Anders Hammar :
>>> See http://jira.codehaus.org/browse/MARCHETYPES-38 (I agree our
>>> sources must have asl header)

Sufficiently small and uncreative files don't qualify for copyright
and so don't need a license header. I choose to believe that these are
those.


>>> But I agree too to not generate sources with asf headers as some users
>>> can use something else.
>>> see the solution here: http://svn.apache.org/r1414907
>>>
>>
>> The generated source in the quickstart archetype does not have any kind of
>> license header.
> yup I have never said MARCHETYPES-38 was fixed :-)
>>
>> /Anders
>>
>>
>>>
>>>
>>> >
>>> > /Anders
>>> >
>>> >
>>> > On Wed, Nov 28, 2012 at 2:32 PM, Anders Hammar 
>>> wrote:
>>> >
>>> >> Nope, I'm +1 with everything else. I'll file a ticket for the warning
>>> and
>>> >> fix it.
>>> >>
>>> >> /Anders
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Nov 28, 2012 at 1:59 PM, Olivier Lamy  wrote:
>>> >>
>>> >>> Perso, I won't consider that as blocker.
>>> >>> Any other troubles ?
>>> >>>
>>> >>>
>>> >>>
>>> >>> 2012/11/28 Anders Hammar :
>>> >>> > Testing I now noticed this output:
>>> >>> >
>>> >>> > [WARNING]
>>> >>> >
>>> >>> > Goal prefix is specified as: 'archtst-maven-plugin'. Maven currently
>>> >>> > expects it to be 'archtst'.
>>> >>> >
>>> >>> > I never configure goalPrefix, do we need that? As it is now, using
>>> the
>>> >>> > artifactId isn't really correct.
>>> >>> >
>>> >>> > /Anders
>>> >>> >
>>> >>> > On Wed, Nov 28, 2012 at 11:03 AM, Olivier Lamy 
>>> >>> wrote:
>>> >>> >
>>> >>> >> -DarchetypeRepository=
>>> >>> >> https://repository.apache.org/content/repositories/maven-090/
>>> >>> >>
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Olivier Lamy
>>> >>> Talend: http://coders.talend.com
>>> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> >>>
>>> >>> -
>>> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> >>> For additional commands, e-mail: dev-h...@maven.apache.org
>>> >>>
>>> >>>
>>> >>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread John Casey

Found a minor regression:

http://jira.codehaus.org/browse/MNG-5390

It's not critical, but keeps the output from being as helpful as it could.

On 11/28/12 2:52 PM, John Casey wrote:

+1

It appears to work fine on my largest builds here.

On 11/26/12 12:24 AM, Jason van Zyl wrote:

Hi,

Here is a link to Jira with 30 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967


Staging repo:
https://repository.apache.org/content/repositories/maven-073/

The distributable binaries and sources for testing can be found here:
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/


Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip

https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz

https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip

https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz


Staging site:
http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0

The documentation specifically for this release pertains to JSR330 and
SLF4J-based logging:
http://maven.apache.org/maven-jsr330.html
http://maven.apache.org/maven-logging.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.

-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org







--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
GitHub - http://github.com/jdcasey

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[VOTE] Release Maven Enforcer version 1.2

2012-11-28 Thread Paul Gier
Hi,

We solved 10 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=18491

There are still a couple of issues left in JIRA:
https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MENFORCER+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide

Staging repo:
https://repository.apache.org/content/repositories/maven-093/
https://repository.apache.org/content/repositories/maven-093/org/apache/maven/enforcer/enforcer/1.2/enforcer-1.2-source-release.zip

Staging site:
http://maven.apache.org/enforcer-1.2/

SCM Tag:
https://svn.apache.org/repos/asf/maven/enforcer/tags/enforcer-1.2/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Jason van Zyl
Thanks, easy enough to fix. I'll wait until the morning for other comments but 
looks like a re-spin would be a good idea.

On Nov 28, 2012, at 7:18 PM, John Casey  wrote:

> Found a minor regression:
> 
> http://jira.codehaus.org/browse/MNG-5390
> 
> It's not critical, but keeps the output from being as helpful as it could.
> 
> On 11/28/12 2:52 PM, John Casey wrote:
>> +1
>> 
>> It appears to work fine on my largest builds here.
>> 
>> On 11/26/12 12:24 AM, Jason van Zyl wrote:
>>> Hi,
>>> 
>>> Here is a link to Jira with 30 issues resolved:
>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>>> 
>>> 
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-073/
>>> 
>>> The distributable binaries and sources for testing can be found here:
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>>> 
>>> 
>>> Specifically the zip, tarball, and source archives can be found here:
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>>> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>>> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>>> 
>>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>>> 
>>> 
>>> Staging site:
>>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>>> 
>>> The documentation specifically for this release pertains to JSR330 and
>>> SLF4J-based logging:
>>> http://maven.apache.org/maven-jsr330.html
>>> http://maven.apache.org/maven-logging.html
>>> 
>>> Vote open for 72 hours.
>>> 
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
>>> --
>>> Jason van Zyl
>>> Founder & CTO, Sonatype
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> -
>>> 
>>> People develop abstractions by generalizing from concrete examples.
>>> Every attempt to determine the correct abstraction on paper without
>>> actually developing a running system is doomed to failure. No one
>>> is that smart. A framework is a resuable design, so you develop it by
>>> looking at the things it is supposed to be a design of. The more examples
>>> you look at, the more general your framework will be.
>>> 
>>> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>> 
>> 
>> 
> 
> 
> -- 
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> GitHub - http://github.com/jdcasey
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

You are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of 
dogmas or goals, it's always because these dogmas or
goals are in doubt.

  -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance







Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Jason van Zyl
I'm going to re-spin it. Shall I just use 2.2 or wait for you guys to spin 2.4?

On Nov 28, 2012, at 12:54 PM, Daniel Kulp  wrote:

> 
> On Nov 28, 2012, at 12:33 PM, Jason van Zyl  wrote:
>> But what version of the plugin are users going to get?
> 
> If it's not locked down, they would get 2.3.  (maven 3.0.x users get 2.1.3 I 
> think)
> 
> 
> However, I want to be clear:
> 
> * The issue ONLY affects Mac users.  Other platforms are OK.
> 
> * The issue only affects users that use the war plugin.   
> 
> * There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4 is 
> released).  
> 
> * Another work around: adding the -Djava.awt.headless=true flag to the 
> MAVEN_OPTS.
> 
> * The issue does NOT affect the output of the war plugin.  The plugin does 
> exactly what it's supposed to do and produces a proper war.
> 
> 
> The only "problem" is the Java Icon that would appear on the Mac Dock for the 
> duration of the build.   It doesn't affect the actual build at all.   
> 
> So basically, it affects a relatively small number of maven users, doesn't 
> affect the actual build at all, and has a relatively easy workaround for 
> people that are annoyed by it.
> 
> 
> Dan
> 
> 
> 
>> On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:
>> 
>>> 
>>> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier  wrote:
>>> 
 there is an issue opened about it ?
 I didn't find it.
>>> 
>>> No, Olivier and I spent a chunk of time yesterday on IRC trying to figure 
>>> out what was going on.   Once we figured it out, he committed a fix before 
>>> I could even login to JIRA.  :-)
>>> 
>>> 
>>> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1 line
>>> back tp xstream 1.4.2 to avoid http://jira.codehaus.org/browse/XSTR-709
>>> 
>>> 
>>> Dan
>>> 
>>> 
 
 
 On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp  wrote:
 
> 
> +1
> 
> I've tested this with a few projects and it seems to work.
> 
> I DON'T like that it updates the war plugin to 2.3 as that version has
> issues on the Mac related to setting up an awt Toolkit.   However, there 
> is
> a simple workaround of locking the war version down to 2.2 in the project
> pom (which is something the project in question should have done anyway).
> 
> Dan
> 
> 
> 
>> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl  wrote:
>> 
>>> Hi,
>>> 
>>> Here is a link to Jira with 30 issues resolved:
>>> 
>>> 
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>>> 
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-073/
>>> 
>>> The distributable binaries and sources for testing can be found here:
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
>>> 
>>> Specifically the zip, tarball, and source archives can be found here:
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
>>> 
>>> 
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
>>> 
>>> Staging site:
>>> http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
>>> 
>>> The documentation specifically for this release pertains to JSR330 and
>>> SLF4J-based logging:
>>> http://maven.apache.org/maven-jsr330.html
>>> http://maven.apache.org/maven-logging.html
>>> 
>>> Vote open for 72 hours.
>>> 
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
> 
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 
 
 
 -- 
 -
 Arnaud Héritier
 06-89-76-64-24
 http://aheritier.net
 Mail/GTalk: aherit...@gmail.com
 Twitter/Skype : aheritier
>>> 
>>> -- 
>>> Daniel Kulp
>>> dk...@apache.org - http://dankulp.com/blog
>>> Talend Community Coder - http://coders.talend.com
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ---

Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Barrie Treloar
On Thu, Nov 29, 2012 at 10:48 AM, John Casey  wrote:
> Found a minor regression:
>
> http://jira.codehaus.org/browse/MNG-5390
>
> It's not critical, but keeps the output from being as helpful as it could.

Is this something that we have an IT for?

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Jason van Zyl
It definitely needs a unit test, but I don't think that needs an IT. The logger 
can't be null before it's used. We used to resort to checking for null and 
using stdout if so. I thought I got all the paths where it could be null but 
obviously not.

On Nov 28, 2012, at 9:15 PM, Barrie Treloar  wrote:

> On Thu, Nov 29, 2012 at 10:48 AM, John Casey  wrote:
>> Found a minor regression:
>> 
>> http://jira.codehaus.org/browse/MNG-5390
>> 
>> It's not critical, but keeps the output from being as helpful as it could.
> 
> Is this something that we have an IT for?
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Thanks,

Jason

--
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

What matters is not ideas, but the people who have them. Good people can fix 
bad ideas, but good ideas can't save bad people. 

 -- Paul Graham







Re: maven-3 and core-integration-testing git migration, needs verification

2012-11-28 Thread Brett Porter
Looks good. Compared the current state of these to SVN and confirmed they 
match. We have a lot of $Id$ to kill in maven-integration-testing.

Some empty directories removed in maven-3 - hopefully they don't affect 
anything. Particular oddities:
http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/load-extern-profiles-ioex/profiles.xml/
http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/project-parse-ioex/pom.xml

All builds, so should be fine.

Tags and branches look to line up. Looks like the 3.0.4 tag was corrected. I 
note some old branches have been brought back: e.g. 
http://svn.apache.org/viewvc?view=revision&revision=983251. This is probably 
ok, though.

I guess the 3.1.0 tag should be removed from SVN & Git before this is wrapped 
up?

Cheers,
Brett

On 28/11/2012, at 6:52 PM, Kristian Rosenvold  
wrote:

> The repos are located at:
> 
> https://git-wip-us.apache.org/repos/asf/maven.git
> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
> 
> 
> Please "test" them, unless anyone has any objections they will become
> r/w 24 hours from now.
> 
> 
> The "3.1.0" tag is in the git repo, so I suppose this does not affect
> the release unless we have to respin.
> 
> 
> Kristian
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter






-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Stephane Nicoll
I would go for 2.2. Releasing something and then include it as the default
version the same day seems a bit too much for me.

On Thursday, November 29, 2012, Jason van Zyl wrote:

> I'm going to re-spin it. Shall I just use 2.2 or wait for you guys to spin
> 2.4?
>
> On Nov 28, 2012, at 12:54 PM, Daniel Kulp  wrote:
>
> >
> > On Nov 28, 2012, at 12:33 PM, Jason van Zyl  wrote:
> >> But what version of the plugin are users going to get?
> >
> > If it's not locked down, they would get 2.3.  (maven 3.0.x users get
> 2.1.3 I think)
> >
> >
> > However, I want to be clear:
> >
> > * The issue ONLY affects Mac users.  Other platforms are OK.
> >
> > * The issue only affects users that use the war plugin.
> >
> > * There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4
> is released).
> >
> > * Another work around: adding the -Djava.awt.headless=true flag to the
> MAVEN_OPTS.
> >
> > * The issue does NOT affect the output of the war plugin.  The plugin
> does exactly what it's supposed to do and produces a proper war.
> >
> >
> > The only "problem" is the Java Icon that would appear on the Mac Dock
> for the duration of the build.   It doesn't affect the actual build at all.
> >
> > So basically, it affects a relatively small number of maven users,
> doesn't affect the actual build at all, and has a relatively easy
> workaround for people that are annoyed by it.
> >
> >
> > Dan
> >
> >
> >
> >> On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:
> >>
> >>>
> >>> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier 
> wrote:
> >>>
>  there is an issue opened about it ?
>  I didn't find it.
> >>>
> >>> No, Olivier and I spent a chunk of time yesterday on IRC trying to
> figure out what was going on.   Once we figured it out, he committed a fix
> before I could even login to JIRA.  :-)
> >>>
> >>>
> >>> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1
> line
> >>> back tp xstream 1.4.2 to avoid
> http://jira.codehaus.org/browse/XSTR-709
> >>>
> >>>
> >>> Dan
> >>>
> >>>
> 
> 
>  On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp 
> wrote:
> 
> >
> > +1
> >
> > I've tested this with a few projects and it seems to work.
> >
> > I DON'T like that it updates the war plugin to 2.3 as that version
> has
> > issues on the Mac related to setting up an awt Toolkit.   However,
> there is
> > a simple workaround of locking the war version down to 2.2 in the
> project
> > pom (which is something the project in question should have done
> anyway).
> >
> > Dan
> >
> >
> >
> >> On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl 
> wrote:
> >>
> >>> Hi,
> >>>
> >>> Here is a link to Jira with 30 issues resolved:
> >>>
> >>>
> >
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
> >>>
> >>> Staging repo:
> >>> https://repository.apache.org/content/repositories/maven-073/
> >>>
> >>> The distributable binaries and sources for testing can be found
> here:
> >>>
> >>>
> >
> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-the
> course of true love never did run smooth ...
>
>  -- Shakespeare
>
>
>
>
>
>


Re: [VOTE] Maven 3.1.0

2012-11-28 Thread Jason van Zyl
I was just going to wait the 3 days if folks wanted 2.4. It's been 11 months, 
another 3 days isn't a big deal.

jvz

On 2012-11-28, at 10:22 PM, Stephane Nicoll  wrote:

> I would go for 2.2. Releasing something and then include it as the default
> version the same day seems a bit too much for me.
> 
> On Thursday, November 29, 2012, Jason van Zyl wrote:
> 
>> I'm going to re-spin it. Shall I just use 2.2 or wait for you guys to spin
>> 2.4?
>> 
>> On Nov 28, 2012, at 12:54 PM, Daniel Kulp  wrote:
>> 
>>> 
>>> On Nov 28, 2012, at 12:33 PM, Jason van Zyl  wrote:
 But what version of the plugin are users going to get?
>>> 
>>> If it's not locked down, they would get 2.3.  (maven 3.0.x users get
>> 2.1.3 I think)
>>> 
>>> 
>>> However, I want to be clear:
>>> 
>>> * The issue ONLY affects Mac users.  Other platforms are OK.
>>> 
>>> * The issue only affects users that use the war plugin.
>>> 
>>> * There is an easy workaround of locking down to 2.2 (or to 2.4 once 2.4
>> is released).
>>> 
>>> * Another work around: adding the -Djava.awt.headless=true flag to the
>> MAVEN_OPTS.
>>> 
>>> * The issue does NOT affect the output of the war plugin.  The plugin
>> does exactly what it's supposed to do and produces a proper war.
>>> 
>>> 
>>> The only "problem" is the Java Icon that would appear on the Mac Dock
>> for the duration of the build.   It doesn't affect the actual build at all.
>>> 
>>> So basically, it affects a relatively small number of maven users,
>> doesn't affect the actual build at all, and has a relatively easy
>> workaround for people that are annoyed by it.
>>> 
>>> 
>>> Dan
>>> 
>>> 
>>> 
 On Nov 28, 2012, at 11:54 AM, Daniel Kulp  wrote:
 
> 
> On Nov 28, 2012, at 11:46 AM, Arnaud Héritier 
>> wrote:
> 
>> there is an issue opened about it ?
>> I didn't find it.
> 
> No, Olivier and I spent a chunk of time yesterday on IRC trying to
>> figure out what was going on.   Once we figured it out, he committed a fix
>> before I could even login to JIRA.  :-)
> 
> 
> r1414267 | olamy | 2012-11-27 12:09:54 -0500 (Tue, 27 Nov 2012) | 1
>> line
> back tp xstream 1.4.2 to avoid
>> http://jira.codehaus.org/browse/XSTR-709
> 
> 
> Dan
> 
> 
>> 
>> 
>> On Wed, Nov 28, 2012 at 5:33 PM, Daniel Kulp 
>> wrote:
>> 
>>> 
>>> +1
>>> 
>>> I've tested this with a few projects and it seems to work.
>>> 
>>> I DON'T like that it updates the war plugin to 2.3 as that version
>> has
>>> issues on the Mac related to setting up an awt Toolkit.   However,
>> there is
>>> a simple workaround of locking the war version down to 2.2 in the
>> project
>>> pom (which is something the project in question should have done
>> anyway).
>>> 
>>> Dan
>>> 
>>> 
>>> 
 On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl 
>> wrote:
 
> Hi,
> 
> Here is a link to Jira with 30 issues resolved:
> 
> 
>>> 
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-073/
> 
> The distributable binaries and sources for testing can be found
>> here:
> 
> 
>>> 
>> https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-the
>> course of true love never did run smooth ...
>> 
>> -- Shakespeare
>> 
>> 
>> 
>> 
>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org