Re: [VOTE] Release Maven Release plugin version 2.1

2010-10-05 Thread Emmanuel Venisse
+1 Emmanuel On Mon, Oct 4, 2010 at 2:01 PM, Brett Porter br...@apache.org wrote: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source

Re: [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Olivier Lamy
+1 Le 5 octobre 2010 00:44, Arnaud Héritier aherit...@gmail.com a écrit : 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

Re: [VOTE] Release Maven Release plugin version 2.1

2010-10-05 Thread Olivier Lamy
+1 (thanks for pushing this !) 2010/10/4 Brett Porter br...@apache.org: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source distribution:

Re: [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Mark Hobson
It generally works for my builds apart from the behaviour of an internal Maven plugin. This plugin uses the shared component maven-runtime to determine the dependency order of the project's dependencies, which is subtly different between m2.2.1 and m3. I haven't had time to fully debug the

Re: [VOTE] Release Maven Release plugin version 2.1

2010-10-05 Thread Jörg Schaible
Hi Brett, Brett Porter wrote: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source distribution:

Re: [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Baptiste MATHUS
2010/10/5 Mark Hobson markhob...@gmail.com It generally works for my builds apart from the behaviour of an internal Maven plugin. This plugin uses the shared component maven-runtime to determine the dependency order of the project's dependencies, which is subtly different between m2.2.1 and

Re: [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Paul Benedict
+1 works for me. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Release plugin version 2.1

2010-10-05 Thread Brett Porter
On 06/10/2010, at 12:15 AM, Jörg Schaible wrote: Hi Brett, Brett Porter wrote: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/

Re: [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Mark Hobson
On 5 October 2010 14:31, Baptiste MATHUS m...@batmat.net wrote: +1. It'd confirm what I checked yesterday (see my other mail). I was having problem with XML parser due to a different classpath ordering inside surefire between m2.2.1 and m3. As Olivier said, it's true it's bad to rely on

Re : [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Julien HENRY
After trying to migrate JWebUnit build to Maven 3 (especially site section) I think I found a regression: http://jira.codehaus.org/browse/MNG-4852 It seems configuration defined in reportSet section is no more taken into account. Regards, Julien - Message d'origine De : Benjamin

Re: [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Jason van Zyl
On Oct 5, 2010, at 10:04 AM, Mark Hobson wrote: On 5 October 2010 14:31, Baptiste MATHUS m...@batmat.net wrote: +1. It'd confirm what I checked yesterday (see my other mail). I was having problem with XML parser due to a different classpath ordering inside surefire between m2.2.1 and m3.

Re: [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Mark Hobson
On 5 October 2010 15:54, Jason van Zyl ja...@sonatype.com wrote: a DAG which is toposorted is naturally unordered for elements at the same level in a graph.  The set is deterministic, the order of that set is not. Relying on any ordering for something that is naturally unordered is not

[m3] ProjectSorter problems (was: Re: [VOTE] Release Apache Maven 3.0)

2010-10-05 Thread Mark Hobson
Branching the m3 vote thread: On 5 October 2010 16:22, Mark Hobson markhob...@gmail.com wrote: Sorry, I don't think I was clear enough before.  It's not the ordering of elements at the same level that's a problem, it's that the element order is wrong.  I was also meaning deterministic with

Re: [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Dennis Lundberg
+1 from me I've tried it on my private projects and the projects at my day job and all seems well. On 2010-10-04 14: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

Re: Updating the release plan for Assembly Plugin

2010-10-05 Thread Dennis Lundberg
On 2010-10-04 18:44, John Casey wrote: 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

Re: Surefire: empty string in systemPropertyVariables?

2010-10-05 Thread Laird Nelson
I have determined that Surefire's new systemPropertyVariables stanza cannot deal with empty strings and have filed an issue together with a reproducible test case: http://jira.codehaus.org/browse/SUREFIRE-649. Best, Laird

Re: [m3] ProjectSorter problems (was: Re: [VOTE] Release Apache Maven 3.0)

2010-10-05 Thread Mark Hobson
On 5 October 2010 18:35, Mark Hobson markhob...@gmail.com wrote: I've taken a quick look at ProjectSorter in the debugger and it looks like it's skipping vertexes where versions don't match.  For example, if A depends on B:1.0 but B is resolved to 1.1 (via resolution or management) then

Re: [m3] ProjectSorter problems (was: Re: [VOTE] Release Apache Maven 3.0)

2010-10-05 Thread Mark Hobson
On 5 October 2010 21:50, Mark Hobson markhob...@gmail.com wrote: I've raised MNG-4854 [1] to demonstrate the problem. Benjamin, I understand your comment on the issue. The situation I have is with maven-runtime where all dependencies have already been mediated, so project:1.0 is in fact using

Re: [m3] ProjectSorter problems (was: Re: [VOTE] Release Apache Maven 3.0)

2010-10-05 Thread Benjamin Bentmann
Mark Hobson wrote: Is there a way that we could support both behaviours? To me the situation looks like this: The ProjectSorter serves one purpose, that is to figure out the build order of projects within a reactor. Unless I misunderstand, you seem to have a different use case and merely

Re: [m3] ProjectSorter problems (was: Re: [VOTE] Release Apache Maven 3.0)

2010-10-05 Thread Mark Hobson
On 5 October 2010 22:43, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: To me the situation looks like this: The ProjectSorter serves one purpose, that is to figure out the build order of projects within a reactor. Unless I misunderstand, you seem to have a different use case and merely use

Maven 3.0 and Aether

2010-10-05 Thread Hervé BOUTEMY
I like the rewrite of dependency resolution component. And I perfectly understand the objective of hosting it apart from Maven: I hope to see another aether-provider implementation that shows success of this strategy. I have no doubt that if a Maven committer needs to improve Aether, it's easy

Re: Maven 3.0 and Aether

2010-10-05 Thread Kristian Rosenvold
You can add http://github.com/sonatype/sonatype-aether/commits/master.atom to your reader/whatever, it's a a commit feed. But I also suppose this information should be added to some kind of page describing how/what to do with external dependencies (on a slightly more general basis). Is there

Re: [VOTE] Release Apache Maven 3.0

2010-10-05 Thread Brett Porter
+1 There are a couple of issues (MNG-1911, MNG-4850, and various output improvements), but not worth holding this up any longer. It's well overdue. - Brett On 04/10/2010, at 11:16 PM, Benjamin Bentmann wrote: Hi, feedback on the RCs seems to be decreasing and I am currently not aware of