You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2007/09/20 03:31:01 UTC
[proposal] bring plugin tools together in SCM
I'd like to do what we did for surefire and bring all the following
into one tree, called /plugin-tools/trunk, versioned consistently as
2.4 and using MPLUGIN as the JIRA project:
* plugins/maven-plugin-plugin
* shared/maven-plugin-*
* shared/maven-script
Thoughts?
Cheers,
Brett
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
RE: [proposal] bring plugin tools together in SCM
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
+1 seems logical and I can't think of any drawback at this point.
-----Original Message-----
From: Brett Porter [mailto:brett@apache.org]
Sent: Wednesday, September 19, 2007 9:31 PM
To: Maven Developers List
Subject: [proposal] bring plugin tools together in SCM
I'd like to do what we did for surefire and bring all the following
into one tree, called /plugin-tools/trunk, versioned consistently as
2.4 and using MPLUGIN as the JIRA project:
* plugins/maven-plugin-plugin
* shared/maven-plugin-*
* shared/maven-script
Thoughts?
Cheers,
Brett
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [proposal] bring plugin tools together in SCM
Posted by John Casey <jd...@commonjava.org>.
Sounds fine to me. I think this was the point of shared originally,
though I guess the scope was a tad broader (including the apps
themselves, not just plugins). The only concern I would have is to
ensure that this collection only contains things that have no earthly
point other than serving plugins... :-) Otherwise, we're just
confusing people who need a decent helper library.
-john
On Sep 19, 2007, at 9:31 PM, Brett Porter wrote:
> I'd like to do what we did for surefire and bring all the following
> into one tree, called /plugin-tools/trunk, versioned consistently
> as 2.4 and using MPLUGIN as the JIRA project:
> * plugins/maven-plugin-plugin
> * shared/maven-plugin-*
> * shared/maven-script
>
> Thoughts?
>
> Cheers,
> Brett
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
Re: [proposal] bring plugin tools together in SCM
Posted by Mauro Talevi <ma...@aquilonia.org>.
Brett Porter wrote:
> I'd like to do what we did for surefire and bring all the following into
> one tree, called /plugin-tools/trunk, versioned consistently as 2.4 and
> using MPLUGIN as the JIRA project:
> * plugins/maven-plugin-plugin
> * shared/maven-plugin-*
> * shared/maven-script
>
> Thoughts?
>
+1 - seems reasonable to streamline plugin-related tools.
Documentation will then be under http://maven.apache.org/plugin-tools - I suppose.
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [proposal] bring plugin tools together in SCM
Posted by Brett Porter <br...@apache.org>.
... and the maven-plugin-testing-tools since they depend on snapshots
of the invoker and test-tools, neither of which are deployed, and the
invoker doesn't build because of failed tests.
- Brett
On 29/10/2007, at 2:19 PM, Brett Porter wrote:
> I've done this, with the exception of maven-script since it now
> seems to depend on Maven trunk, which would block us releasing
> anything under there.
>
> - Brett
>
> On 20/09/2007, at 11:31 AM, Brett Porter wrote:
>
>> I'd like to do what we did for surefire and bring all the
>> following into one tree, called /plugin-tools/trunk, versioned
>> consistently as 2.4 and using MPLUGIN as the JIRA project:
>> * plugins/maven-plugin-plugin
>> * shared/maven-plugin-*
>> * shared/maven-script
>>
>> Thoughts?
>>
>> Cheers,
>> Brett
>>
>> --
>> Brett Porter - brett@apache.org
>> Blog: http://www.devzuz.org/blogs/bporter/
>>
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [proposal] bring plugin tools together in SCM
Posted by Brett Porter <br...@apache.org>.
On 29/10/2007, at 3:22 PM, Jason van Zyl wrote:
>
> On 28 Oct 07, at 8:19 PM 28 Oct 07, Brett Porter wrote:
>
>> I've done this, with the exception of maven-script since it now
>> seems to depend on Maven trunk, which would block us releasing
>> anything under there.
>>
>
> I just took the copy from trunk, if it is coupled to trunk I'll fix
> that as it shouldn't be.
I tried flipping it back to 2.0.7 but it doesn't compile - I think it
uses some new things in the plugin descriptor?
I have to admit I haven't taken a long look at it - but I do recall
John doing some work there.
- Brett
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [proposal] bring plugin tools together in SCM
Posted by Jason van Zyl <ja...@maven.org>.
On 28 Oct 07, at 8:19 PM 28 Oct 07, Brett Porter wrote:
> I've done this, with the exception of maven-script since it now
> seems to depend on Maven trunk, which would block us releasing
> anything under there.
>
I just took the copy from trunk, if it is coupled to trunk I'll fix
that as it shouldn't be.
> - Brett
>
> On 20/09/2007, at 11:31 AM, Brett Porter wrote:
>
>> I'd like to do what we did for surefire and bring all the following
>> into one tree, called /plugin-tools/trunk, versioned consistently
>> as 2.4 and using MPLUGIN as the JIRA project:
>> * plugins/maven-plugin-plugin
>> * shared/maven-plugin-*
>> * shared/maven-script
>>
>> Thoughts?
>>
>> Cheers,
>> Brett
>>
>> --
>> Brett Porter - brett@apache.org
>> Blog: http://www.devzuz.org/blogs/bporter/
>>
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [proposal] bring plugin tools together in SCM
Posted by Brett Porter <br...@apache.org>.
I've done this, with the exception of maven-script since it now seems
to depend on Maven trunk, which would block us releasing anything
under there.
- Brett
On 20/09/2007, at 11:31 AM, Brett Porter wrote:
> I'd like to do what we did for surefire and bring all the following
> into one tree, called /plugin-tools/trunk, versioned consistently
> as 2.4 and using MPLUGIN as the JIRA project:
> * plugins/maven-plugin-plugin
> * shared/maven-plugin-*
> * shared/maven-script
>
> Thoughts?
>
> Cheers,
> Brett
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org