> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 22 October 2003 09:17
> To: 'Maven Developers List'
> Subject: RE: Moving plugins
>
>
> > I will also take responsibility for moving the summit plugin
> > and the u
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 22 October 2003 08:41
> To: Maven Developers List
> Subject: Re: Moving plugins
[snip]
> The touchstone could probably even go. I'm going to out a proposal
where
> the names of go
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 22 October 2003 09:05
> To: Maven Developers List
> Subject: Re: Moving plugins
>
> Yo,
>
> There are also some plugins that we should push out of the nest.
>
> I was just chatti
> I will also take responsibility for moving the summit plugin
> and the uberjar plugin and move them into summit and
> classworlds respectively.
>
Can we just make sure that the doco still get links from Maven so users can
come through the maven site to see a fairly large list of plugins. I t
On Wed, 2003-10-22 at 03:04, Jason van Zyl wrote:
> Yo,
>
> There are also some plugins that we should push out of the nest.
>
> I was just chatting with Martin (a torque committer) to try and take
> responsibility for the Maven torque plugin and I think the same could be
> done with the Cactus p
> It shouldn't require that the plugins have maven as their
> groupId, i.e. if
> it's javaapp:blah, and the javaapp plugin is
Yeah, the extra groupId is only needed if there is a conflict I imagine. And
the maven one can take precedence :)
> At the moment we're waiting on Brett checking in a ne
Jason van Zyl <[EMAIL PROTECTED]> wrote on 22/10/2003 04:40:37 PM:
[snip good stuff]
> The touchstone could probably even go. I'm going to out a proposal where
> the names of goals are done in such a way that we follow the once
> established convention of : (e.g. jar:build). With this
> the goal
Yo,
There are also some plugins that we should push out of the nest.
I was just chatting with Martin (a torque committer) to try and take
responsibility for the Maven torque plugin and I think the same could be
done with the Cactus plugin where we have Apache projects with Maven
plugins.
The pro
On Wed, 2003-10-22 at 02:45, Brett Porter wrote:
> > These below should go as well. The coupling on the license
> > plugin needs to be removed, multiproject certainly isn't
> > core, and neither is plugin.
> >
> > > - license
> > > - multiproject
> > > - touchstone
> > > - touchstone-partner
> >
> These below should go as well. The coupling on the license
> plugin needs to be removed, multiproject certainly isn't
> core, and neither is plugin.
>
> > - license
> > - multiproject
> > - touchstone
> > - touchstone-partner
> > - plugin
Isn't touchstone needed to test the maven code though?
On Wed, 2003-10-22 at 00:57, [EMAIL PROTECTED] wrote:
> I'd like to move the following plugins out of the core cvs module:
>
> - artifact
> - caller
> - changelog
> - changes
> - checkstyle
> - deploy
> - developer-activity
> - dist
> - ear
> - ejb
> - faq
> - file-activity
> - javadoc
> - jdepend
> > I wonder if it is also worth putting all of the report only plugins
> > into
> a
> > separate subdirectory.
>
> What about plugins that are report and something else like
> the javadoc
> plugin?
Yeah, you are right. If we are going to go down the categorisation path,
best do it properly a
Brett Porter <[EMAIL PROTECTED]> wrote on 22/10/2003 03:14:52 PM:
> +0, although I'm not sure what makes multiproject core.
Cool. I missed that one somehow. It's not used in bootstrap, so it could
move too.
> I wonder if it is also worth putting all of the report only plugins into
a
> separat
+0
Why don't you also move the multiplugin project?
Thanks
-Vincent
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 22 October 2003 06:58
> To: [EMAIL PROTECTED]
> Subject: Moving plugins
>
> I'd like to move the following plugins out of the core cvs mod
+0, although I'm not sure what makes multiproject core.
I wonder if it is also worth putting all of the report only plugins into a
separate subdirectory.
You'll need to be careful that there aren't any issues with dynatag
libraries too, I think a couple of core ones still specify xmlns:deploy,
ev
Peter Donald wrote:
On Thu, 9 Oct 2003 12:17 am, Florin Vancea wrote:
If I may say something before it's too late: Maybe there is a need for a LATEST on each (or on several) branch (es).
Something like
log4j
log4j
LATEST
should get the latest-and-gratest, but something like
log4j
log
On Thu, 9 Oct 2003 12:17 am, Florin Vancea wrote:
> If I may say something before it's too late: Maybe there is a need for a
> LATEST on each (or on several) branch (es).
>
> Something like
>
>
> log4j
> log4j
> LATEST
>
>
> should get the latest-and-gratest, but something like
>
>
> log
van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 08 October 2003 07:41
> > To: Maven Developers List
> > Subject: RE: Moving Plugins
> >
> > On Wed, 2003-10-08 at 02:53, Vincent Massol wrote:
> >
> > > Agreed. In my opinion we should do both. We already start
- Original Message -
From: "Jason van Zyl" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, October 08, 2003 8:30 AM
Subject: RE: Moving Plugins
> > - also, now that plugins are externalized it will be more di
Do you want me to move the one I listed in my previous mail or do you
want to do it?
Thanks
-Vincent
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2003 07:41
> To: Maven Developers List
> Subject: RE: Moving Plugins
>
> On
On Wed, 2003-10-08 at 02:53, Vincent Massol wrote:
> Agreed. In my opinion we should do both. We already started the plugin
> move; we should finish it and not let it lie in mid-air.
Many have been moved and I've offered help to anyone who has plugins and
wants them moved. I have moved my own an
On Wed, 2003-10-08 at 01:39, Vincent Massol wrote:
> Hi Jason,
>
> I'm fine with moving the following: Cactus, checkstyle, jboss, pmd,
> statcvs and actually all the other remaining plugins... I still don't
> understand why we need to keep any plugin at all in maven core. They can
> be downloaded
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2003 09:10
> To: Maven Developers List
> Subject: RE: Moving Plugins
[snip]
> > In addition, adding this declaration will download the maven jar
which
> > is unnecessar
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 08/10/2003 04:53:36 PM:
[snip]
> Agreed. In my opinion we should do both. We already started the plugin
> move; we should finish it and not let it lie in mid-air. I shall be able
> to help more in about 1-2 week's time now that my JUnit book is going to
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2003 08:03
> To: Maven Developers List
> Subject: RE: Moving Plugins
>
> "Vincent Massol" <[EMAIL PROTECTED]> wrote on 08/10/2003 03:39:23
PM:
>
> &
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 08/10/2003 03:39:23 PM:
> Hi Jason,
>
> I'm fine with moving the following: Cactus, checkstyle, jboss, pmd,
> statcvs and actually all the other remaining plugins... I still don't
> understand why we need to keep any plugin at all in maven core. They
Hi Jason,
I'm fine with moving the following: Cactus, checkstyle, jboss, pmd,
statcvs and actually all the other remaining plugins... I still don't
understand why we need to keep any plugin at all in maven core. They can
be downloaded for bootstrapping (in the same way as all the other jars
are).
round
that never get run anyway.
- Brett
> -Original Message-
> From: Steve Garcia [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 8 October 2003 10:18 AM
> To: 'Maven Developers List'
> Subject: RE: Moving Plugins
>
>
> Just to clarify, where are the non-co
Just to clarify, where are the non-core plugins being moved to? Are they no
longer going to be part of the maven src tree?
Thanks!
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 07, 2003 1:09 PM
> To: Maven Developers List
> Subject: Moving
29 matches
Mail list logo
