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,
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 sh
... 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-scrip
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, c
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 -
+1 seems logical and I can't think of any drawback at this point.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
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 su
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 servin
