You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Vincent Siveton <vi...@gmail.com> on 2008/03/08 16:24:39 UTC
[proposal] Plugin tools and shared reorganization
Hi,
According recent threads on plugin-tools, I propose to:
* create a new SCM entry for maven/plugin-testing which will include
maven-plugin-testing-harness, maven-plugin-testing-tools and
maven-test-tools
* created a new groupId for them, ie org.apache.maven.plugin.testingtools
* created a new groupId for plugin-tools, ie
org.apache.maven.plugintools and align version to 2.4-SNAPSHOT
Thoughts?
Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [proposal] Plugin tools and shared reorganization
Posted by Vincent Siveton <vi...@gmail.com>.
Hi,
I finished the move in r636149. Waiting for MPA-110.
Snapshots are deployed.
Cheers,
Vincent
2008/3/8, Vincent Siveton <vi...@gmail.com>:
> Hi,
>
> Yes. The Jira projects will be:
> * plugintools: MPLUGIN (or MPA-107 if someone think it will be better)
> * testingtools: see MPA-110
>
> Cheers,
>
> Vincent
>
>
> 2008/3/8, Brian E. Fox <br...@reply.infinity.nu>:
>
> > Just so we're clear, each of these trees will have a single jira project
> > (with each child as a component) and they will be released together as a
> > unit?
> >
> > With that clarification, +1
> >
> >
> > -----Original Message-----
> > From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> > Sent: Saturday, March 08, 2008 10:25 AM
> > To: Maven Developers List
> > Subject: [proposal] Plugin tools and shared reorganization
> >
> > Hi,
> >
> > According recent threads on plugin-tools, I propose to:
> > * create a new SCM entry for maven/plugin-testing which will include
> > maven-plugin-testing-harness, maven-plugin-testing-tools and
> > maven-test-tools
> > * created a new groupId for them, ie
> > org.apache.maven.plugin.testingtools
> > * created a new groupId for plugin-tools, ie
> > org.apache.maven.plugintools and align version to 2.4-SNAPSHOT
> >
> > Thoughts?
> >
> > Vincent
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [proposal] Plugin tools and shared reorganization
Posted by Vincent Siveton <vi...@gmail.com>.
Hi,
Yes. The Jira projects will be:
* plugintools: MPLUGIN (or MPA-107 if someone think it will be better)
* testingtools: see MPA-110
Cheers,
Vincent
2008/3/8, Brian E. Fox <br...@reply.infinity.nu>:
> Just so we're clear, each of these trees will have a single jira project
> (with each child as a component) and they will be released together as a
> unit?
>
> With that clarification, +1
>
>
> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> Sent: Saturday, March 08, 2008 10:25 AM
> To: Maven Developers List
> Subject: [proposal] Plugin tools and shared reorganization
>
> Hi,
>
> According recent threads on plugin-tools, I propose to:
> * create a new SCM entry for maven/plugin-testing which will include
> maven-plugin-testing-harness, maven-plugin-testing-tools and
> maven-test-tools
> * created a new groupId for them, ie
> org.apache.maven.plugin.testingtools
> * created a new groupId for plugin-tools, ie
> org.apache.maven.plugintools and align version to 2.4-SNAPSHOT
>
> Thoughts?
>
> Vincent
>
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [proposal] Plugin tools and shared reorganization
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Just so we're clear, each of these trees will have a single jira project
(with each child as a component) and they will be released together as a
unit?
With that clarification, +1
-----Original Message-----
From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
Sent: Saturday, March 08, 2008 10:25 AM
To: Maven Developers List
Subject: [proposal] Plugin tools and shared reorganization
Hi,
According recent threads on plugin-tools, I propose to:
* create a new SCM entry for maven/plugin-testing which will include
maven-plugin-testing-harness, maven-plugin-testing-tools and
maven-test-tools
* created a new groupId for them, ie
org.apache.maven.plugin.testingtools
* created a new groupId for plugin-tools, ie
org.apache.maven.plugintools and align version to 2.4-SNAPSHOT
Thoughts?
Vincent
---------------------------------------------------------------------
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