On Thu, 2005-05-26 at 16:32 +1000, Brett Porter wrote:
> Hi,
>
> Given the resounding mess that resulted from giving each plugin its own
> project in JIRA for m1, I'd like to propose the following for m2:
>
> - create a maven-plugins project
> - add new plugins as components
> - add a "component
Stephane Nicoll wrote:
If you guys can afford one projet per plugin, I would suggest to go
that way.
I don't think we can afford to add any more, but we could probably reuse
the m1 plugins with new version identifiers... I'd just find that very
confusing as they are completely different, for
If you guys can afford one projet per plugin, I would suggest to go
that way. Maybe, we can give differents rights to different people
(e.g. one project manager per plugin).
Have you thinked of Fix For Version? I agree with Vincent when he says
that plugins do not share the same dev/release lifecy
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: jeudi 26 mai 2005 08:33
> To: Maven Developers List
> Subject: JIRA proposal for plugins
>
> Hi,
>
> Given the resounding mess that resulted from giving each plugin its own
> pro
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: jeudi 26 mai 2005 08:33
> To: Maven Developers List
> Subject: JIRA proposal for plugins
>
> Hi,
>
> Given the resounding mess that resulted from giving each plugin its own
> pro
Hi,
Given the resounding mess that resulted from giving each plugin its own
project in JIRA for m1, I'd like to propose the following for m2:
- create a maven-plugins project
- add new plugins as components
- add a "component version" field that is free text.
Upside:
- more manageable
- can s
