I think
for now we should move the testing-harness back out of the tools and
then create a new plugin-testing structure. There's not a good reason to
mix runtime plugin tools and things only used to test the plugins.
+1
Benjamin
7:32 PM
To: Maven Developers List
Subject: RE: [Vote] Release Maven Plugin Tools projects
"I was young and dumb and needed the money..."
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2008 7:03 PM
To: Maven Developers List
Subject: Re: [Vote]
ven Plugin Tools projects
"I was young and dumb and needed the money..."
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2008 7:03 PM
To: Maven Developers List
Subject: Re: [Vote] Release Maven Plugin Tools projects
On 07/03/2008, at 10
"I was young and dumb and needed the money..."
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2008 7:03 PM
To: Maven Developers List
Subject: Re: [Vote] Release Maven Plugin Tools projects
On 07/03/2008, at 10:34 AM, Brian E. Fox w
]
:)
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2008 6:31 PM
To: Maven Developers List
Subject: Re: [Vote] Release Maven Plugin Tools projects
Will MPLUGIN and plugin tools have different release cycles?
Well, they already had: There
Maven Plugin Tools projects
> Will MPLUGIN and plugin tools have different release cycles?
Well, they already had: There is maven-plugin-plugin 2.1, 2.2 and 2.3 in
central but only maven-plugin-tools-api/maven-plugin-tools-java 2.1.
Benja
Will MPLUGIN and plugin tools have different release cycles?
Well, they already had: There is maven-plugin-plugin 2.1, 2.2 and 2.3 in
central but only maven-plugin-tools-api/maven-plugin-tools-java 2.1.
Benjamin
-
To unsub
2008/3/6, Dennis Lundberg <[EMAIL PROTECTED]>:
> Vincent Siveton wrote:
> > Hi,
> >
> > 2008/3/6, Brett Porter <[EMAIL PROTECTED]>:
> >> Just to understand - does that mean you're going to re-align the
> >> versions and leave the JIRA project as one?
> >>
> >
> > Nope. I proposed to create
Vincent Siveton wrote:
Hi,
2008/3/6, Brett Porter <[EMAIL PROTECTED]>:
Just to understand - does that mean you're going to re-align the
versions and leave the JIRA project as one?
Nope. I proposed to create a new jira project for plugin tools (see MPA-107).
MPLUGIN will be for the Maven plu
Hi Dennis,
2008/3/6, Dennis Lundberg <[EMAIL PROTECTED]>:
> I think this is partially my fault. When Vincent bought up the idea of
> aligning the groupIds within the plugin tolls, I gave a few reasons for
> *not* doing that. So Vincent reverted that commit.
You were the only one to answer and y
Hi,
2008/3/6, Brett Porter <[EMAIL PROTECTED]>:
> Just to understand - does that mean you're going to re-align the
> versions and leave the JIRA project as one?
>
Nope. I proposed to create a new jira project for plugin tools (see MPA-107).
MPLUGIN will be for the Maven plugin.
Cheers,
Vincent
I think this is partially my fault. When Vincent bought up the idea of
aligning the groupIds within the plugin tolls, I gave a few reasons for
*not* doing that. So Vincent reverted that commit.
However, I think that also reverted the aligning of versions (to
2.4-SNAPSHOT) in pom files that had
Just to understand - does that mean you're going to re-align the
versions and leave the JIRA project as one?
(maybe the old versions in JIRA could signify which version of the
plugin and which of the tools like we did with surefire until the
versions were aligned)
Thanks,
Brett
On 07/03/
Thanks Benjamin. I will call a new vote soon.
Cheers,
Vincent
2008/3/6, Benjamin Bentmann <[EMAIL PROTECTED]>:
> > The Maven Plugin Tools projects are ready to be released.
>
>
> -1, due to the issues I just filled in, especially MPLUGIN-89.
>
> I apologize for checking things so late but it's
Thanks Brett.
Vincent
2008/3/6, Brett Porter <[EMAIL PROTECTED]>:
>
> On 07/03/2008, at 3:29 AM, Benjamin Bentmann wrote:
>
> >> * maven-plugin-tools-api-2.2
> >
> > According to JIRA, the maven-plugin-tools-api-2.2 was released
> > 2006-12-29:
> >
> http://jira.codehaus.org/browse/MPLUGIN
Hi Benjamin,
2008/3/6, Benjamin Bentmann <[EMAIL PROTECTED]>:
> > * maven-plugin-tools-api-2.2
>
>
> According to JIRA, the maven-plugin-tools-api-2.2 was released 2006-12-29:
>
> http://jira.codehaus.org/browse/MPLUGIN/component/13118?selected=com.atlassian.jira.plugin.system.project:component-
On 07/03/2008, at 3:29 AM, Benjamin Bentmann wrote:
* maven-plugin-tools-api-2.2
According to JIRA, the maven-plugin-tools-api-2.2 was released
2006-12-29:
http://jira.codehaus.org/browse/MPLUGIN/component/13118?selected=com.atlassian.jira.plugin.system.project:component-changelog-panel
C
The Maven Plugin Tools projects are ready to be released.
-1, due to the issues I just filled in, especially MPLUGIN-89.
I apologize for checking things so late but it's mostly child diseases and
easy to fix.
Benjamin
-
* maven-plugin-tools-api-2.2
According to JIRA, the maven-plugin-tools-api-2.2 was released 2006-12-29:
http://jira.codehaus.org/browse/MPLUGIN/component/13118?selected=com.atlassian.jira.plugin.system.project:component-changelog-panel
Cleaning up JIRA to get in sync with the POMs and the actua
On 3/6/08, Vincent Siveton <[EMAIL PROTECTED]> wrote:
> Hi,
>
> The Maven Plugin Tools projects are ready to be released. It includes
> the following sub-projects:
> * maven-plugin-plugin-2.4
I'm worry it might be too late but..
Is there a chance to change image for marking 'non reports' goals
Hi,
The Maven Plugin Tools projects are ready to be released. It includes
the following sub-projects:
* maven-plugin-plugin-2.4
* maven-plugin-tools-beanshell-2.2
* maven-plugin-testing-harness-1.2
* maven-plugin-tools-java-2.2
* maven-plugin-tools-2.2
* maven-plugin-tools-javadoc-1.0
* maven-plug
21 matches
Mail list logo
