Re: svn commit: r1004461 - in /maven/plugins/trunk/maven-antrun-plugin/src: it/task-encoding-test/ it/task-encoding-test/pom.xml main/java/org/apache/maven/plugin/antrun/AntRunMojo.java

[Benjamin Bentmann]

Hi Paul,


Author: pgier
Date: Mon Oct  4 22:22:30 2010
New Revision: 1004461

URL: http://svn.apache.org/viewvc?rev=1004461&view=rev
Log:
[MANTRUN-155] Set encoding for generated Ant build.  Patch from Anders Hammar 
with some minor changes.

Added:
 maven/plugins/trunk/maven-antrun-plugin/src/it/task-encoding-test/
 maven/plugins/trunk/maven-antrun-plugin/src/it/task-encoding-test/pom.xml  
 (with props)
Modified:
 
maven/plugins/trunk/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/antrun/AntRunMojo.java

+String encoding = project.getProperties().getProperty( 
"project.build.sourceEncoding" );
+if ( encoding == null )
+{
+encoding = DEFAULT_ANT_BUILD_ENCODING;
+}


This approach violates the usual usage pattern for the source encoding 
as outlined in [0]. First, the direct query to the property cuts off the 
future migration to a POM element. Second, the default value for the 
property is not UTF-8 but the platform encoding.


Given that the build file for Ant is auto-generated and not meant for 
human consumption/editing, I don't see any reason why its encoding 
should be configurable by the user and be linked to the sourceEncoding 
property. As such, why not keept it simple and just always use UTF-8 for 
the encoding? Always using UTF-8 also ensures that the build file can be 
written at all, even if project.build.encoding is set to a charset that 
can't represent the characters given in the POM.



Benjamin


[0] 
http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding.


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

Re: [VOTE] Release Apache Maven 3.0

[Arnaud Héritier]

Tested on various projects.
+1

Arnaud 

On Oct 4, 2010, at 2:16 PM, Benjamin Bentmann wrote:

> Hi,
> 
> feedback on the RCs seems to be decreasing and I am currently not aware of 
> any major regression so let's try and cross the finishing line of this 
> marathon.
> 
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from me
> 
> 
> Benjamin
> 
> -
> 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] Release Apache Maven 3.0

[Ralph Goers]

-0.  I have the same objection to Aether that I noted when it was introduced. 
It is now much more difficult for me to enhance dependency resolution in Maven 
to include metadata beyond what the Aether api supports since Aether is not 
part of Maven.

Ralph

On Oct 4, 2010, at 5:16 AM, Benjamin Bentmann wrote:

> Hi,
> 
> feedback on the RCs seems to be decreasing and I am currently not aware of 
> any major regression so let's try and cross the finishing line of this 
> marathon.
> 
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from me
> 
> 
> Benjamin
> 
> -
> 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] Release Apache Maven 3.0

[Hilco Wijbenga]

On 4 October 2010 05:16, Benjamin Bentmann  wrote:
> feedback on the RCs seems to be decreasing and I am currently not aware of
> any major regression so let's try and cross the finishing line of this
> marathon.

I seem to have a problem with a combination of Maven 2 and 3:

http://mail-archives.apache.org/mod_mbox/maven-users/201010.mbox/browser

In summary, it works with Maven 3 but not with Maven 2 (any more). It
was suggested I bring it up here. I would greatly appreciate your
comments (not here, of course, but on the users list).

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

Re: [VOTE] Release Apache Maven 3.0

[Evgeny Mandrikov]

+1 (non binding)

Tested on all Sonar projects including parallel builds and Tycho-based.

On Mon, Oct 4, 2010 at 21:57, Toni Menzel  wrote:

> +1 (non binding)  OPS4J stuff builds on and works with this cool release!
>
> Toni
>
> On Mon, Oct 4, 2010 at 7:50 PM, Hervé BOUTEMY 
> wrote:
> > +1
> >
> > Hervé
> >
> > Le lundi 04 octobre 2010, Benjamin Bentmann a écrit :
> >> Hi,
> >>
> >> feedback on the RCs seems to be decreasing and I am currently not aware
> >> of any major regression so let's try and cross the finishing line of
> >> this marathon.
> >>
> >> We solved 31 issues since 3.0-beta-3:
> >>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13
> >> 142
> >>
> >> There are still a couple of issues left in JIRA:
> >>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&st
> >> atus=1
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-004/
> >>
> >> Staged source and binary distros:
> >>
> https://repository.apache.org/content/repositories/maven-004/org/apache/mav
> >> en/apache-maven/3.0/
> >>
> >> Guide to testing staged releases:
> >> http://maven.apache.org/guides/development/guide-testing-releases.html
> >>
> >> Vote open for 72 hours.
> >>
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1
> >>
> >> +1 from me
> >>
> >>
> >> Benjamin
> >>
> >> -
> >> 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
> >
> >
>
>
>
> --
> Toni Menzel || http://okidokiteam.com
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Best regards,
Evgeny Mandrikov aka Godin 
http://twitter.com/_godin_

Re: [VOTE] Release Maven Release plugin version 2.1

[Mark Derricutt]

+1
-- 
Pull me down under...



On Tue, Oct 5, 2010 at 1:01 AM, Brett Porter  wrote:

> Hi,
>
> We solved 17 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&styleName=Html&version=12571
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-002/
>
> Source distribution:
>
> https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip
>
> SCM tag:
> http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1
>
> Staging site:
> http://maven.apache.org/plugins/maven-release-plugin-2.1/
> http://maven.apache.org/maven-release/staging/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Cheers,
> Brett
>
>
> --
> Brett Porter
> br...@apache.org
> http://brettporter.wordpress.com/
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven 3.0

[Toni Menzel]

+1 (non binding)  OPS4J stuff builds on and works with this cool release!

Toni

On Mon, Oct 4, 2010 at 7:50 PM, Hervé BOUTEMY  wrote:
> +1
>
> Hervé
>
> Le lundi 04 octobre 2010, Benjamin Bentmann a écrit :
>> Hi,
>>
>> feedback on the RCs seems to be decreasing and I am currently not aware
>> of any major regression so let's try and cross the finishing line of
>> this marathon.
>>
>> We solved 31 issues since 3.0-beta-3:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13
>> 142
>>
>> There are still a couple of issues left in JIRA:
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&st
>> atus=1
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-004/
>>
>> Staged source and binary distros:
>> https://repository.apache.org/content/repositories/maven-004/org/apache/mav
>> en/apache-maven/3.0/
>>
>> Guide to testing staged releases:
>> http://maven.apache.org/guides/development/guide-testing-releases.html
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>> +1 from me
>>
>>
>> Benjamin
>>
>> -
>> 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
>
>



-- 
Toni Menzel || http://okidokiteam.com

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

Re: [VOTE] Release Apache Maven 3.0

[Hervé BOUTEMY]

+1

Hervé

Le lundi 04 octobre 2010, Benjamin Bentmann a écrit :
> Hi,
> 
> feedback on the RCs seems to be decreasing and I am currently not aware
> of any major regression so let's try and cross the finishing line of
> this marathon.
> 
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13
> 142
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&st
> atus=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/mav
> en/apache-maven/3.0/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from me
> 
> 
> Benjamin
> 
> -
> 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] Release Apache Maven 3.0

[Jesse Glick]

Nonbinding +1; seems to be working well embedded in NetBeans IDE development 
builds. Nice job.


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

Re: Inflexibility of --also-make w.r.t. unusual goals

[Jesse Glick]

On 10/02/2010 07:27 AM, Brett Porter wrote:

Are there plans for a more clever make mode? The 3.0 compatibility guide 
implies that there are, but does not give any specifics.


I'm not sure what you're referring to that gave that indication?


https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-LegacystyleReactorModeusingIncludes/Excludes
 [BTW anchor link in TOC is broken]

"Future development will focus on improvements to the make-like reactor mode that 
provides similar functionality but is aware of the project hierarchy."


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

[RESULT] [VOTE] Release Maven Common Artifact Filters version 1.3

[John Casey]

Re-sending to copy the PMC list.

The vote has passed with the following result :

+1 (binding): John, Olivier, Benjamin, Herve

I will promote the artifacts to the central repo.


On 9/28/10 6:31 PM, John Casey wrote:

Hi,

We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=15582


There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=component+%3D+maven-common-artifact-filters+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC



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

Staging site:
http://maven.apache.org/shared/maven-common-artifact-filters-1.3/

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

Vote open for 72 hours.

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

Here's my +1.



--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/

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

Re: [VOTE] Release Maven Common Artifact Filters version 1.3

[John Casey]

Hi,
The vote has passed with the following result :

+1 (binding): John, Olivier, Benjamin, Herve

I will promote the artifacts to the central repo.


On 9/28/10 6:31 PM, John Casey wrote:

Hi,

We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=15582


There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=component+%3D+maven-common-artifact-filters+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC



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

Staging site:
http://maven.apache.org/shared/maven-common-artifact-filters-1.3/

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

Vote open for 72 hours.

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

Here's my +1.



--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/

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

Re: Updating the release plan for Assembly Plugin

[John Casey]

Sorry I missed this thread before...

On 9/15/10 1:28 PM, Dennis Lundberg wrote:

Hi

I saw that John added http://jira.codehaus.org/browse/MASSEMBLY-502 with
a wish for Java 1.5. This is fine, but I think we need to discuss the
contents of the coming versions.

Over the last year or so I've tried to get rid of as many alpha and beta
plugins as possible. We are now down to only 4 remaining, and the
Assembly plugin is one of them. In my opinion alpha and beta versions of
plugins only adds to the version confusion for our users.

Now to the Assembly plugin. Here's what we have in JIRA:

2.2-beta-6: 4 out of 23 issues fixed
2.2:0 out of 14 issues fixed
2.3-beta-1: 0 out of 14 issues fixed

I propose that we shuffle these around:

- Skip 2.2-beta-6, the next version will be 2.2
- 2.2 will contain the 4 issues already solved for 2.2-beta-6, and
anything else (small) that we can cram in there without disturbing too
much. Remember that it won't be beta any more :-)
- The version after that will be 2.3 (not a beta), which will require
Java 1.5


IMO, we've got a base version of Maven 2.x that's been out for what? two 
years? ...and it requires 1.5. Using generics makes the code _much_ 
cleaner, as do things like varargs, so I think it's worthwhile to make 
this switch for the 2.2 release instead of waiting.


What's the big advantage to holding this back?


- If necessary 2.2.x releases can be branched off, while trunk continues
towards 2.3


Comments?



At any rate, my first attempt to release the 2.2 version of this plugin 
has failed with a problem unit test on windows. If we need to discuss 
this further, we have an opportunity.


--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/

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

Re: [VOTE] Release Apache Maven 3.0

[Igor Fedorenko]

+1. maven 3.0 looks good on tycho.

--
Regards,
Igor

Benjamin Bentmann wrote:

Hi,

feedback on the RCs seems to be decreasing and I am currently not aware 
of any major regression so let's try and cross the finishing line of 
this marathon.


We solved 31 issues since 3.0-beta-3:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142 



There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1 



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

Staged source and binary distros:
https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/ 



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

Vote open for 72 hours.

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

+1 from me


Benjamin

-
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] Release Apache Maven 3.0

[Robert Scholte]

+1 (non-binding)
 
> Date: Mon, 4 Oct 2010 17:33:04 +0200
> Subject: Re: [VOTE] Release Apache Maven 3.0
> From: m...@batmat.net
> To: dev@maven.apache.org
> 
> (non-binding.Sorry)
> 
> 2010/10/4 Baptiste MATHUS 
> 
> > +1
> >
> > After fixing our conf (many xml parsers in the classpath), maven 3.0 built
> > them fine, so it's not blocking at all. I'll have to internally investigate
> > where the difference comes from, if possible I might file the corresponding
> > issue once analyzed.
> >
> > Baptiste
> >
> > 2010/10/4 Stephane Nicoll 
> >
> > +1
> >>
> >> Stéphane
> >>
> >> On Mon, Oct 4, 2010 at 2:16 PM, Benjamin Bentmann <
> >> benjamin.bentm...@udo.edu
> >> > wrote:
> >>
> >> > Hi,
> >> >
> >> > feedback on the RCs seems to be decreasing and I am currently not aware
> >> of
> >> > any major regression so let's try and cross the finishing line of this
> >> > marathon.
> >> >
> >> > We solved 31 issues since 3.0-beta-3:
> >> >
> >> >
> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> >> >
> >> > There are still a couple of issues left in JIRA:
> >> >
> >> >
> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> >> >
> >> > Staging repo:
> >> > https://repository.apache.org/content/repositories/maven-004/
> >> >
> >> > Staged source and binary distros:
> >> >
> >> >
> >> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
> >> >
> >> > Guide to testing staged releases:
> >> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >> >
> >> > Vote open for 72 hours.
> >> >
> >> > [ ] +1
> >> > [ ] +0
> >> > [ ] -1
> >> >
> >> > +1 from me
> >> >
> >> >
> >> > Benjamin
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: dev-h...@maven.apache.org
> >> >
> >> >
> >>
> >
> >
> >
> > --
> > Baptiste  MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
> >
> 
> 
> 
> -- 
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
  

Re: [VOTE] Release Apache Maven 3.0

[Baptiste MATHUS]

(non-binding.Sorry)

2010/10/4 Baptiste MATHUS 

> +1
>
> After fixing our conf (many xml parsers in the classpath), maven 3.0 built
> them fine, so it's not blocking at all. I'll have to internally investigate
> where the difference comes from, if possible I might file the corresponding
> issue once analyzed.
>
> Baptiste
>
> 2010/10/4 Stephane Nicoll 
>
> +1
>>
>> Stéphane
>>
>> On Mon, Oct 4, 2010 at 2:16 PM, Benjamin Bentmann <
>> benjamin.bentm...@udo.edu
>> > wrote:
>>
>> > Hi,
>> >
>> > feedback on the RCs seems to be decreasing and I am currently not aware
>> of
>> > any major regression so let's try and cross the finishing line of this
>> > marathon.
>> >
>> > We solved 31 issues since 3.0-beta-3:
>> >
>> >
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>> >
>> > There are still a couple of issues left in JIRA:
>> >
>> >
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/maven-004/
>> >
>> > Staged source and binary distros:
>> >
>> >
>> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
>> >
>> > Guide to testing staged releases:
>> > http://maven.apache.org/guides/development/guide-testing-releases.html
>> >
>> > Vote open for 72 hours.
>> >
>> > [ ] +1
>> > [ ] +0
>> > [ ] -1
>> >
>> > +1 from me
>> >
>> >
>> > Benjamin
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>> >
>>
>
>
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Re: [VOTE] Release Apache Maven 3.0

[Baptiste MATHUS]

+1

After fixing our conf (many xml parsers in the classpath), maven 3.0 built
them fine, so it's not blocking at all. I'll have to internally investigate
where the difference comes from, if possible I might file the corresponding
issue once analyzed.

Baptiste

2010/10/4 Stephane Nicoll 

> +1
>
> Stéphane
>
> On Mon, Oct 4, 2010 at 2:16 PM, Benjamin Bentmann <
> benjamin.bentm...@udo.edu
> > wrote:
>
> > Hi,
> >
> > feedback on the RCs seems to be decreasing and I am currently not aware
> of
> > any major regression so let's try and cross the finishing line of this
> > marathon.
> >
> > We solved 31 issues since 3.0-beta-3:
> >
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-004/
> >
> > Staged source and binary distros:
> >
> >
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > +1 from me
> >
> >
> > Benjamin
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Re: [VOTE] Release Apache Maven 3.0

[Stephane Nicoll]

+1

Stéphane

On Mon, Oct 4, 2010 at 2:16 PM, Benjamin Bentmann  wrote:

> Hi,
>
> feedback on the RCs seems to be decreasing and I am currently not aware of
> any major regression so let's try and cross the finishing line of this
> marathon.
>
> We solved 31 issues since 3.0-beta-3:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
>
> Staged source and binary distros:
>
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> +1 from me
>
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven 3.0

[Paul Merlin]

+1 (non-binding)


/Paul

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

Re: [VOTE] Release Apache Maven 3.0

[Daniel Kulp]

+1

Dan


On Monday 04 October 2010 8:16:07 am Benjamin Bentmann wrote:
> Hi,
> 
> feedback on the RCs seems to be decreasing and I am currently not aware
> of any major regression so let's try and cross the finishing line of
> this marathon.
> 
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13
> 142
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&st
> atus=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/mav
> en/apache-maven/3.0/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from me
> 
> 
> Benjamin
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org

-- 
Daniel Kulp
dk...@apache.org
http://dankulp.com/blog

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

Re: [VOTE] Release Apache Maven 3.0

[Jesse McConnell]

+1 go go maven gadgets!

--
jesse mcconnell
jesse.mcconn...@gmail.com



On Mon, Oct 4, 2010 at 09:57, Vincent Siveton  wrote:
> yeah +1
>
> Vincent
>
> 2010/10/4 Benjamin Bentmann :
>> Hi,
>>
>> feedback on the RCs seems to be decreasing and I am currently not aware of
>> any major regression so let's try and cross the finishing line of this
>> marathon.
>>
>> We solved 31 issues since 3.0-beta-3:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>>
>> There are still a couple of issues left in JIRA:
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-004/
>>
>> Staged source and binary distros:
>> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
>>
>> Guide to testing staged releases:
>> http://maven.apache.org/guides/development/guide-testing-releases.html
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>> +1 from me
>>
>>
>> Benjamin
>>
>> -
>> 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
>
>

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

Re: [VOTE] Release Apache Maven 3.0

[Vincent Siveton]

yeah +1

Vincent

2010/10/4 Benjamin Bentmann :
> Hi,
>
> feedback on the RCs seems to be decreasing and I am currently not aware of
> any major regression so let's try and cross the finishing line of this
> marathon.
>
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
>
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> +1 from me
>
>
> Benjamin
>
> -
> 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] Release Apache Maven 3.0

[John Casey]

+1

On 10/4/10 8:16 AM, Benjamin Bentmann wrote:

Hi,

feedback on the RCs seems to be decreasing and I am currently not aware
of any major regression so let's try and cross the finishing line of
this marathon.

We solved 31 issues since 3.0-beta-3:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142


There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1


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

Staged source and binary distros:
https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/


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

Vote open for 72 hours.

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

+1 from me


Benjamin

-
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)
Blog: http://www.johnofalltrades.name/

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

Re: Release plugin snapshot dependency resolution

[Brett Porter]

On 04/10/2010, at 6:06 PM, Marcus Linke wrote:

> OK accepted. But if this shouldn't be within the responsibility of the
> release plugin but of the versions plugin, do you know a possibility to
> hide this versions plugin goal execution from the users point of view? So
> is there a way to hook in the versions plugin goal execution into the
> release process to automate this? Maybe the release plugin should at least
> be configurable to execute some goals AFTER the release creation phase as
> this can be done with the '-Dgoals'
> (http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#goals)
> option WHILE the release creation phase ? I think this should be a good
> (because generic) solution. What do you think?

I do agree with this - whether for this use case or not, I think a change to 
the release plugin to be able to run goals at the end of preparation would be 
useful to start breaking up some of the functionality into discreet tasks. 
That's a new issue for the release plugin though :)

- Brett

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





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

Re: [VOTE] Release Apache Maven 3.0

[Stephen Connolly]

+1

Stephen

On 4 October 2010 15:06, Emmanuel Venisse wrote:

> +1
>
> Emmanuel
>
> On Mon, Oct 4, 2010 at 2:16 PM, Benjamin Bentmann <
> benjamin.bentm...@udo.edu
> > wrote:
>
> > Hi,
> >
> > feedback on the RCs seems to be decreasing and I am currently not aware
> of
> > any major regression so let's try and cross the finishing line of this
> > marathon.
> >
> > We solved 31 issues since 3.0-beta-3:
> >
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-004/
> >
> > Staged source and binary distros:
> >
> >
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > +1 from me
> >
> >
> > Benjamin
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: Release plugin snapshot dependency resolution

[Brett Porter]

On 04/10/2010, at 10:36 PM, Marcus Linke wrote:

> Hi brett, of course it is. So should i open a new issue for this feature
> in the JIRA or will you do so? ;) 

It's all yours.

- Brett

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





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

Re: [PLEASE TEST] Apache Maven 3.0-RC3

[Olivier Lamy]

Hi,
Not sure it's a maven issue here.
You can try changing the sax parser
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl

with a recent xerces version in your classpath (in your pom I mean)

In the gwt plugin configuration use

...-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
...

HTH,
-- 
Olivier
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

2010/10/4 Baptiste MATHUS :
> Hi,
>
> I just tested maven3 on a project I hadn't tried before and notice a build
> failure that doesn't happen with mvn2.2.1.
> It seems to be related to XML parser problem&GWTTestCase.
> I suspect it might be related to classpath ordering, though I remember this
> order must be guaranteed since 2.0.9.
>
> I'd like to use dependency:list to check ordering, but I remember (Arnaud's
> tweet, I'd say) reading that the dependency plugin output is not reliable
> yet with maven3 execution? Is it?
>
> What are the possible ways to be able to debug it?
>
> Cheers
> PS :
> The full stacktrace:
> [ERROR] Failure while parsing XML
> org.xml.sax.SAXNotRecognizedException:
> http://apache.org/xml/features/nonvalidating/load-external-dtd
> at
> oracle.xml.jaxp.JXSAXParserFactory.setFeature(JXSAXParserFactory.java:128)
> at
> com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:320)
> at
> com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$100(ReflectiveParser.java:48)
> at
> com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:398)
> at
> com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:257)
> at com.google.gwt.dev.cfg.ModuleDefLoader$2.load(ModuleDefLoader.java:187)
> at
> com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:283)
> at
> com.google.gwt.dev.cfg.ModuleDefLoader.createSyntheticModule(ModuleDefLoader.java:95)
> at
> com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl2(CompileStrategy.java:169)
> at
> com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl(CompileStrategy.java:116)
> at
> com.google.gwt.junit.SimpleCompileStrategy.maybeCompileModule(CompileStrategy.java:330)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1296)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1265)
> at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:620)
> at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:456)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:311)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:140)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017)
>   [ERROR] Unexpected error while processing XML
>
> 2010/10/2 Benjamin Bentmann 
>
>> Robert Scholte wrote:
>>
>>      [INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ mojo-parent
>>> ---
>>>     GPG Passphrase: *
>>> gpg: can't open
>>> `D:\java-workspace\helios\mojo-parent\target\mojo-parent-26-site.xml': No
>>> such file or directory
>>>     gpg: signing failed: file open error
>>>
>>
>> This is neither a bug in Maven, the Release Plugin nor the GPG Plugin but
>> the Site Plugin:
>>
>> http://jira.codehaus.org/browse/MSITE-508
>>
>>
>> Benjamin
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>

Re: Release plugin snapshot dependency resolution

[Marcus Linke]

Hi brett, of course it is. So should i open a new issue for this feature
in the JIRA or will you do so? ;) 

"Maven Developers List"  writes:
>On 04/10/2010, at 6:06 PM, Marcus Linke wrote:
>
>> OK accepted. But if this shouldn't be within the responsibility of the
>> release plugin but of the versions plugin, do you know a possibility to
>> hide this versions plugin goal execution from the users point of view?
>So
>> is there a way to hook in the versions plugin goal execution into the
>> release process to automate this? Maybe the release plugin should at
>least
>> be configurable to execute some goals AFTER the release creation phase
>as
>> this can be done with the '-Dgoals'
>>
>(http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#goals)
>> option WHILE the release creation phase ? I think this should be a good
>> (because generic) solution. What do you think?
>
>I do agree with this - whether for this use case or not, I think a change
>to the release plugin to be able to run goals at the end of preparation
>would be useful to start breaking up some of the functionality into
>discreet tasks. That's a new issue for the release plugin though :)
>
>- Brett
>
>--
>Brett Porter
>br...@apache.org
>http://brettporter.wordpress.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] Release Apache Maven 3.0

[nicolas de loof]

+1,

works fine for me
Nicolas

2010/10/4 Greg Akins 

> +1
>
> Ran against all my projects successfully
>
> On Mon, Oct 4, 2010 at 8:16 AM, Benjamin Bentmann
>  wrote:
> > Hi,
> >
> > feedback on the RCs seems to be decreasing and I am currently not aware
> of
> > any major regression so let's try and cross the finishing line of this
> > marathon.
> >
> > We solved 31 issues since 3.0-beta-3:
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> >
> > There are still a couple of issues left in JIRA:
> >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-004/
> >
> > Staged source and binary distros:
> >
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > +1 from me
> >
> >
> > Benjamin
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
>
>
> --
> Greg Akins
>
> http://insomnia-consulting.org
> http://www.pghcodingdojo.org
> http://pittjug.dev.java.net
> http://twitter.com/akinsgre
> http://www.linkedin.com/in/akinsgre
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [PLEASE TEST] Apache Maven 3.0-RC3

[Siarhei Dudzin]

Just fyi, the change in classpah ordering actually helped me to find a
conflict there. Been testing RC3 since its been out - all is good so far.

Regards,
Siarhei
On Oct 4, 2010 3:01 PM, "Benjamin Bentmann" 
wrote:
> Baptiste MATHUS wrote:
>
>> I'd like to use dependency:list to check ordering, but I remember
(Arnaud's
>> tweet, I'd say) reading that the dependency plugin output is not reliable
>> yet with maven3 execution? Is it?
>
> Regardless of the Maven version, dependency:list cannot be used to check
> class path ordering because it sorts its output alphabetically.
>
> I suggest you enable debug logging and check the class path printed to
> the console by the plugin in question, i.e. the Surefire Plugin in your
> case.
>
> In general, you should avoid duplicate classes/dependencies on the class
> path and not rely on any order to solve conflicts.
>
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

Re: [VOTE] Release Apache Maven 3.0

[Emmanuel Venisse]

+1

Emmanuel

On Mon, Oct 4, 2010 at 2:16 PM, Benjamin Bentmann  wrote:

> Hi,
>
> feedback on the RCs seems to be decreasing and I am currently not aware of
> any major regression so let's try and cross the finishing line of this
> marathon.
>
> We solved 31 issues since 3.0-beta-3:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
>
> Staged source and binary distros:
>
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> +1 from me
>
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven 3.0

[Greg Akins]

+1

Ran against all my projects successfully

On Mon, Oct 4, 2010 at 8:16 AM, Benjamin Bentmann
 wrote:
> Hi,
>
> feedback on the RCs seems to be decreasing and I am currently not aware of
> any major regression so let's try and cross the finishing line of this
> marathon.
>
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
>
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> +1 from me
>
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>



-- 
Greg Akins

http://insomnia-consulting.org
http://www.pghcodingdojo.org
http://pittjug.dev.java.net
http://twitter.com/akinsgre
http://www.linkedin.com/in/akinsgre

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

Re: [VOTE] Release Apache Maven 3.0

[Jason van Zyl]

+1

Let it be free!

On Oct 4, 2010, at 8:16 AM, Benjamin Bentmann wrote:

> Hi,
> 
> feedback on the RCs seems to be decreasing and I am currently not aware of 
> any major regression so let's try and cross the finishing line of this 
> marathon.
> 
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from me
> 
> 
> Benjamin
> 
> -
> 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,  Apache Maven
http://twitter.com/jvanzyl
-

We all have problems. How we deal with them is a measure of our worth.

 -- Unknown

[VOTE] Release Apache Maven 3.0

[Benjamin Bentmann]

Hi,

feedback on the RCs seems to be decreasing and I am currently not aware 
of any major regression so let's try and cross the finishing line of 
this marathon.


We solved 31 issues since 3.0-beta-3:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142

There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1

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

Staged source and binary distros:
https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/

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

Vote open for 72 hours.

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

+1 from me


Benjamin

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

Re: [PLEASE TEST] Apache Maven 3.0-RC3

[Benjamin Bentmann]

Baptiste MATHUS wrote:


I'd like to use dependency:list to check ordering, but I remember (Arnaud's
tweet, I'd say) reading that the dependency plugin output is not reliable
yet with maven3 execution? Is it?


Regardless of the Maven version, dependency:list cannot be used to check 
class path ordering because it sorts its output alphabetically.


I suggest you enable debug logging and check the class path printed to 
the console by the plugin in question, i.e. the Surefire Plugin in your 
case.


In general, you should avoid duplicate classes/dependencies on the class 
path and not rely on any order to solve conflicts.



Benjamin

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

Re : [VOTE] Release Apache Maven 3.0

[Julien HENRY]

+1 (non-binding)

I use it everyday on my dev computer. Missing functionalities are Hudson, Sonar 
and m2eclipse (simple) integration but I feel it will be quickly done once 
Maven 
3 is officially released.

Thanks for the good work!

Julien



- Message d'origine 
> De : Benjamin Bentmann 
> À : Maven Developers List 
> Envoyé le : Lun 4 octobre 2010, 14h 16min 07s
> Objet : [VOTE] Release Apache Maven 3.0
> 
> Hi,
> 
> feedback on the RCs seems to be decreasing and I am currently not  aware of 
> any 
>major regression so let's try and cross the finishing line of this  marathon.
> 
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> 
> There  are still a couple of issues left in JIRA:
>http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>1
> 
> Staging  repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged  source and binary distros:
>https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
>/
> 
> Guide  to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote  open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from  me
> 
> 
> Benjamin
> 
> -
> 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: Release plugin snapshot dependency resolution

[Marcus Linke]

OK accepted. But if this shouldn't be within the responsibility of the
release plugin but of the versions plugin, do you know a possibility to
hide this versions plugin goal execution from the users point of view? So
is there a way to hook in the versions plugin goal execution into the
release process to automate this? Maybe the release plugin should at least
be configurable to execute some goals AFTER the release creation phase as
this can be done with the '-Dgoals'
(http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#goals)
option WHILE the release creation phase ? I think this should be a good
(because generic) solution. What do you think?

"Maven Developers List"  writes:
>On 30/09/2010, at 7:05 PM, Marcus Linke wrote:
>
>> For my own usecase where we have strongly coupled projects and usually
>> changes are made in both projects we desire behavior b) but other users
>> would like prefer behavior a).
>
>Understood, but we're talking about the default behaviour, and it seems
>clear that it should be discouraging strongly coupled projects. If they
>are released together all the time, you're much better off to put them in
>the same release unit and release in one move.
>
>> This depends on the project structure i
>> think. So this behavior should be configurable by the user (maybe as a
>> plugin?). This would give us the possibility to define the desired
>> behavior per project. One would argue that switching to the next
>snapshot
>> is not the responsibility of the release plugin but for my own usecase
>> manually switching the dependencies to the next development version is
>> tedious and error-prone. One solution could be to integrate
>functionality
>> of the maven-versions-plugin here that collects its version information
>> from the real repository and allows the user to define the desired
>> behavior.
>> 
>> Any Comments?
>
>In that practice, it's probably best you use the versions plugin you've
>described as part of your release process. I think integrating it into
>the release plugin is probably overkill.
>
>Thanks for your contribution to the issues!
>
>- Brett
>
>--
>Brett Porter
>br...@apache.org
>http://brettporter.wordpress.com/
>
>
>
>
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>For additional commands, e-mail: dev-h...@maven.apache.org
>
>



Mit freundlichen Grüßen

Marcus Linke

--

Softwareentwicklung, IT
news aktuell GmbH - Ein Unternehmen der dpa-Gruppe
Mittelweg 144, 20148 Hamburg
Tel: +49 (0)40-4113-2588
Fax: +49 (0)40-4113-2595

www.newsaktuell.de
www.presseportal.de

www.newsaktuell.de/blog
www.twitter.com/newsaktuell
www.youtube.com/newsaktuell 
www.facebook.com/pages/newsaktuell/152372075544
www.friendfeed.com/newsaktuell

--

Registergericht: Hamburg, Registernummer: HRB 42 738
Umsatzsteuer-Identifikationsnummer gemäß § 27 a Umsatzsteuergesetz:
DE118617411
Vertretungsberechtigte Personen: Carl-Eduard Meyer (Geschäftsführer),
Frank Stadthoewer (Geschäftsführer)


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

Re: [PLEASE TEST] Apache Maven 3.0-RC3

[Baptiste MATHUS]

Hi,

I just tested maven3 on a project I hadn't tried before and notice a build
failure that doesn't happen with mvn2.2.1.
It seems to be related to XML parser problem&GWTTestCase.
I suspect it might be related to classpath ordering, though I remember this
order must be guaranteed since 2.0.9.

I'd like to use dependency:list to check ordering, but I remember (Arnaud's
tweet, I'd say) reading that the dependency plugin output is not reliable
yet with maven3 execution? Is it?

What are the possible ways to be able to debug it?

Cheers
PS :
The full stacktrace:
[ERROR] Failure while parsing XML
org.xml.sax.SAXNotRecognizedException:
http://apache.org/xml/features/nonvalidating/load-external-dtd
at
oracle.xml.jaxp.JXSAXParserFactory.setFeature(JXSAXParserFactory.java:128)
at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:320)
at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$100(ReflectiveParser.java:48)
at
com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:398)
at
com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:257)
at com.google.gwt.dev.cfg.ModuleDefLoader$2.load(ModuleDefLoader.java:187)
at
com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:283)
at
com.google.gwt.dev.cfg.ModuleDefLoader.createSyntheticModule(ModuleDefLoader.java:95)
at
com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl2(CompileStrategy.java:169)
at
com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl(CompileStrategy.java:116)
at
com.google.gwt.junit.SimpleCompileStrategy.maybeCompileModule(CompileStrategy.java:330)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1296)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1265)
at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:620)
at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:456)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:311)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.Surefire.run(Surefire.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017)
   [ERROR] Unexpected error while processing XML

2010/10/2 Benjamin Bentmann 

> Robert Scholte wrote:
>
>  [INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ mojo-parent
>> ---
>> GPG Passphrase: *
>> gpg: can't open
>> `D:\java-workspace\helios\mojo-parent\target\mojo-parent-26-site.xml': No
>> such file or directory
>> gpg: signing failed: file open error
>>
>
> This is neither a bug in Maven, the Release Plugin nor the GPG Plugin but
> the Site Plugin:
>
> http://jira.codehaus.org/browse/MSITE-508
>
>
> Benjamin
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

[VOTE] Release Maven Release plugin version 2.1

[Brett Porter]

Hi,

We solved 17 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&styleName=Html&version=12571

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

Source distribution:
https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip

SCM tag:
http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1

Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.1/
http://maven.apache.org/maven-release/staging/

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

Vote open for 72 hours.

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

Cheers,
Brett


--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





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

Re: [VOTE] Release Apache Maven 3.0

[Stuart McCulloch]

On 4 October 2010 13:16, Benjamin Bentmann wrote:

> Hi,
>
> feedback on the RCs seems to be decreasing and I am currently not aware of
> any major regression so let's try and cross the finishing line of this
> marathon.
>
> We solved 31 issues since 3.0-beta-3:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
>
> Staged source and binary distros:
>
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> +1 from me
>

+1 (non-binding)


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

Re: [PLEASE TEST] Apache Maven 3.0-RC3

[Baptiste MATHUS]

Well, I agree that it's basically not a maven specific issue, but the thing
is the build is going completely fine with 2.2.1, but not with 3.0rc3, so
I'm trying to understand where the difference lies.

And for the record, yes, it's a xml parser problem (oracle xmlparserv2 gets
in the way). I just configured exclusions and then it builds fine.

Sure, I could leave this exclusion here and check if it's also ok with mvn2,
but I'm quite reluctant to do that since it might hide a real isolation or
classpath ordering problem imo.

Cheers

2010/10/4 Olivier Lamy 

> Hi,
> Not sure it's a maven issue here.
> You can try changing the sax parser
>
> -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
>
> with a recent xerces version in your classpath (in your pom I mean)
>
> In the gwt plugin configuration use
>
>
> ...-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
> ...
>
> HTH,
> --
> Olivier
> http://twitter.com/olamy
> http://www.linkedin.com/in/olamy
>
> 2010/10/4 Baptiste MATHUS :
> > Hi,
> >
> > I just tested maven3 on a project I hadn't tried before and notice a
> build
> > failure that doesn't happen with mvn2.2.1.
> > It seems to be related to XML parser problem&GWTTestCase.
> > I suspect it might be related to classpath ordering, though I remember
> this
> > order must be guaranteed since 2.0.9.
> >
> > I'd like to use dependency:list to check ordering, but I remember
> (Arnaud's
> > tweet, I'd say) reading that the dependency plugin output is not reliable
> > yet with maven3 execution? Is it?
> >
> > What are the possible ways to be able to debug it?
> >
> > Cheers
> > PS :
> > The full stacktrace:
> > [ERROR] Failure while parsing XML
> > org.xml.sax.SAXNotRecognizedException:
> > http://apache.org/xml/features/nonvalidating/load-external-dtd
> > at
> >
> oracle.xml.jaxp.JXSAXParserFactory.setFeature(JXSAXParserFactory.java:128)
> > at
> >
> com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:320)
> > at
> >
> com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$100(ReflectiveParser.java:48)
> > at
> >
> com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:398)
> > at
> >
> com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:257)
> > at
> com.google.gwt.dev.cfg.ModuleDefLoader$2.load(ModuleDefLoader.java:187)
> > at
> >
> com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:283)
> > at
> >
> com.google.gwt.dev.cfg.ModuleDefLoader.createSyntheticModule(ModuleDefLoader.java:95)
> > at
> >
> com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl2(CompileStrategy.java:169)
> > at
> >
> com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl(CompileStrategy.java:116)
> > at
> >
> com.google.gwt.junit.SimpleCompileStrategy.maybeCompileModule(CompileStrategy.java:330)
> > at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1296)
> > at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1265)
> > at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:620)
> > at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:456)
> > at junit.framework.TestCase.runBare(TestCase.java:127)
> > at junit.framework.TestResult$1.protect(TestResult.java:106)
> > at junit.framework.TestResult.runProtected(TestResult.java:124)
> > at junit.framework.TestResult.run(TestResult.java:109)
> > at junit.framework.TestCase.run(TestCase.java:118)
> > at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:311)
> > at junit.framework.TestSuite.runTest(TestSuite.java:208)
> > at junit.framework.TestSuite.run(TestSuite.java:203)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> >
> org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
> > at
> >
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
> > at
> >
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:140)
> > at org.apache.maven.surefire.Surefire.run(Surefire.java:109)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> >
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
> > at
> >
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017)
> >   [ERROR] Unexpected error while processing XML
> >
> > 2010/10/2 Benjamin Bentmann 
> >
> >> Robert Scholte wrote

Re: [VOTE] Release Apache Maven 3.0

[chemit]

+1 (non-binding)

Works fine for our projects.

Great job guys.

Le Mon, 04 Oct 2010 14:16:07 +0200,
Benjamin Bentmann  a écrit :

> Hi,
> 
> feedback on the RCs seems to be decreasing and I am currently not
> aware of any major regression so let's try and cross the finishing
> line of this marathon.
> 
> We solved 31 issues since 3.0-beta-3:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from me
> 
> 
> Benjamin
> 
> -
> 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: [PLEASE TEST] Apache Maven 3.0-RC3

[Siarhei Dudzin]

Just fyi, the change in classpah ordering actually helped me to find a
conflict there. Been testing RC3 since its been out - all is good so far.

Regards,
Siarhei
On Oct 4, 2010 3:01 PM, "Benjamin Bentmann" 
wrote: