Re: releasing 2.0.10?

2009-01-29 Thread Paul Benedict
I don't think it's wise to EOL a product without a GA replacement. It's true that because 2.1 is in milestone releases it is not usable by many people in an "approved" managerial environment, but, to the same token, it's not feature complete either. Personally speaking, I definitely am eagerly awa

[jira] Subscription: Design & Best Practices

2009-01-29 Thread jira
Issue Subscription Filter: Design & Best Practices (28 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles http://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

Re: 2.1.x enhancements/fixes and trunk

2009-01-29 Thread Brett Porter
Since trunk is going to be 3.0-SNAPSHOT in between alphas, I needed to take a slightly different approach. In that case (,3.0-alpha-1) will still trigger it, but [3.0-alpha-2,) will not (for those issues that are later fixed). What I did was changed the IT base class to ignore -SNAPSHOT - i

Re: releasing 2.0.10?

2009-01-29 Thread Brett Porter
On 28/01/2009, at 9:03 AM, Brian E. Fox wrote: Normally I would agree on the late change, but it's entirely optional usage so it wouldn't affect existing builds and I'd like to start thinking about 2.0.10 being the EOL for 2.0.x. Given there's already been a good number of fixes for 2.0.11 th

Re: MNG-1957: profile activation, version range syntax

2009-01-29 Thread Torben S. Giesselmann
I was wondering: why isn't the negation operator part of the version range syntax anyways? It's just a matter of keeping the syntax simple - it doesn't add functionality since you can express the same with alternate range boundries. Agreed. And there's something else: what would an expressio

Re: MNG-1957: profile activation, version range syntax

2009-01-29 Thread Brett Porter
On 30/01/2009, at 5:14 AM, Torben S. Giesselmann wrote: Heya, I just submitted a patch which allows using the artifact version range syntax for activating profiles by JDK version. The implementation remains compatible to the way it's currently done (prefix matching), but now also allows

Re: svn commit: r738893 - in /maven/components/sisbell-plugin-manager: maven-project-builder/src/main/java/org/apache/maven/project/builder/ maven-project/src/main/java/org/apache/maven/project/buil

2009-01-29 Thread Shane Isbell
Thanks. Got it. On Thu, Jan 29, 2009 at 11:06 AM, Brett Porter wrote: > > On 30/01/2009, at 2:26 AM, sisb...@apache.org wrote: > > Author: sisbell >> Date: Thu Jan 29 15:26:30 2009 >> New Revision: 738893 >> >> URL: http://svn.apache.org/viewvc?rev=738893&view=rev >> > > > Hi Shane, I think you

Re: svn commit: r738893 - in /maven/components/sisbell-plugin-manager: maven-project-builder/src/main/java/org/apache/maven/project/builder/ maven-project/src/main/java/org/apache/maven/project/builde

2009-01-29 Thread Brett Porter
On 30/01/2009, at 2:26 AM, sisb...@apache.org wrote: Author: sisbell Date: Thu Jan 29 15:26:30 2009 New Revision: 738893 URL: http://svn.apache.org/viewvc?rev=738893&view=rev Hi Shane, I think you forgot the 'branches' part of the URL when this was created - can you move it over please?

Re: svn commit: r737976 - in /maven/repository-tools/trunk/src/bin: crontab.txt synchronize-inbound.sh

2009-01-29 Thread Carlos Sanchez
I changed the crontab, the sync was not having place cd $HOME/bin/synchronize/synchronize-inbound On Mon, Jan 26, 2009 at 6:25 PM, wrote: > Author: brianf > Date: Tue Jan 27 02:25:34 2009 > New Revision: 737976 > > URL: http://svn.apache.org/viewvc?rev=737976&view=rev > Log: > pull inbound syn

MNG-1957: profile activation, version range syntax

2009-01-29 Thread Torben S. Giesselmann
Heya, I just submitted a patch which allows using the artifact version range syntax for activating profiles by JDK version. The implementation remains compatible to the way it's currently done (prefix matching), but now also allows using the negation operator "!" in conjunction with version r

Re: 2.1.x enhancements/fixes and trunk

2009-01-29 Thread Brian Fox
The range should simply skip 3.0alpha1 and 2 --Brian (mobile) On Jan 29, 2009, at 12:45 AM, Arnaud HERITIER wrote: What i understand in brett's email is that its patches are for 2.1 branch but he would like to add ITs to check those fixes in 2.1. His question seems to be if he has to