You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by jv...@apache.org on 2006/09/27 14:41:43 UTC

svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

Author: jvanzyl
Date: Wed Sep 27 05:41:42 2006
New Revision: 450421

URL: http://svn.apache.org/viewvc?view=rev&rev=450421
Log: (empty)

Added:
    maven/shared/trunk/maven-toolchain/
      - copied from r450379, maven/components/branches/maven-2.1-jvz/maven-toolchain/
    maven/shared/trunk/maven-toolchain/pom.xml
      - copied unchanged from r450409, maven/components/branches/maven-2.1-jvz/maven-toolchain/pom.xml
    maven/shared/trunk/maven-toolchain/src/
      - copied from r450409, maven/components/branches/maven-2.1-jvz/maven-toolchain/src/


Re: svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

Posted by Brett Porter <br...@apache.org>.
I really don't know how you are going to provision the toolchains  
without something in the settings which means core changes, but I'll  
see what you come up with.

I'm not sure about using properties in that fashion, really - maybe  
this is just a change to a simpler plugin configuration for now, and  
then a POM element can be introduced in 2.1 that removes the need for  
any plugin configuration when it is set at a project level?

- Brett

On 28/09/2006, at 4:21 AM, Jason van Zyl wrote:

>
> On 27 Sep 06, at 2:50 PM 27 Sep 06, Brett Porter wrote:
>
>> not always the way we've done it, but I wonder if these should  
>> start in the sandbox?
>>
>> Regardless - won't this require POM changes making it depend on 2.1?
>>
>
> No, not if we standardize on a common property as a transition  
> which can be a general strategy for a lot of new POM elements like  
> categories and tags.
>
> Jason.
>
>> - Brett
>>
>> On 27/09/2006, at 10:41 PM, jvanzyl@apache.org wrote:
>>
>>> Author: jvanzyl
>>> Date: Wed Sep 27 05:41:42 2006
>>> New Revision: 450421
>>>
>>> URL: http://svn.apache.org/viewvc?view=rev&rev=450421
>>> Log: (empty)
>>>
>>> Added:
>>>     maven/shared/trunk/maven-toolchain/
>>>       - copied from r450379, maven/components/branches/maven-2.1- 
>>> jvz/maven-toolchain/
>>>     maven/shared/trunk/maven-toolchain/pom.xml
>>>       - copied unchanged from r450409, maven/components/branches/ 
>>> maven-2.1-jvz/maven-toolchain/pom.xml
>>>     maven/shared/trunk/maven-toolchain/src/
>>>       - copied from r450409, maven/components/branches/maven-2.1- 
>>> jvz/maven-toolchain/src/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> Jason van Zyl
> jason@maven.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org

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


Re: svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

Posted by Jason van Zyl <ja...@maven.org>.
On 27 Sep 06, at 2:50 PM 27 Sep 06, Brett Porter wrote:

> not always the way we've done it, but I wonder if these should  
> start in the sandbox?
>
> Regardless - won't this require POM changes making it depend on 2.1?
>

No, not if we standardize on a common property as a transition which  
can be a general strategy for a lot of new POM elements like  
categories and tags.

Jason.

> - Brett
>
> On 27/09/2006, at 10:41 PM, jvanzyl@apache.org wrote:
>
>> Author: jvanzyl
>> Date: Wed Sep 27 05:41:42 2006
>> New Revision: 450421
>>
>> URL: http://svn.apache.org/viewvc?view=rev&rev=450421
>> Log: (empty)
>>
>> Added:
>>     maven/shared/trunk/maven-toolchain/
>>       - copied from r450379, maven/components/branches/maven-2.1- 
>> jvz/maven-toolchain/
>>     maven/shared/trunk/maven-toolchain/pom.xml
>>       - copied unchanged from r450409, maven/components/branches/ 
>> maven-2.1-jvz/maven-toolchain/pom.xml
>>     maven/shared/trunk/maven-toolchain/src/
>>       - copied from r450409, maven/components/branches/maven-2.1- 
>> jvz/maven-toolchain/src/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Jason van Zyl
jason@maven.org




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


Re: svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

Posted by Brett Porter <br...@apache.org>.
not always the way we've done it, but I wonder if these should start  
in the sandbox?

Regardless - won't this require POM changes making it depend on 2.1?

- Brett

On 27/09/2006, at 10:41 PM, jvanzyl@apache.org wrote:

> Author: jvanzyl
> Date: Wed Sep 27 05:41:42 2006
> New Revision: 450421
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=450421
> Log: (empty)
>
> Added:
>     maven/shared/trunk/maven-toolchain/
>       - copied from r450379, maven/components/branches/maven-2.1- 
> jvz/maven-toolchain/
>     maven/shared/trunk/maven-toolchain/pom.xml
>       - copied unchanged from r450409, maven/components/branches/ 
> maven-2.1-jvz/maven-toolchain/pom.xml
>     maven/shared/trunk/maven-toolchain/src/
>       - copied from r450409, maven/components/branches/maven-2.1- 
> jvz/maven-toolchain/src/

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