Summary:
We have 4 binding votes (Carlos, Brett, Vincent M, Arnaud, Lukas) and
one non-binding (Stephane) for demoting the following plugins:
[] repository - (move create-upload-bundle to artifact)
[] release - (move used classes to scm)
[] j2ee - (move resolver tag into ear and j2ee:validate-wa
ok to move it to the core plugins.
I think (but I'm not sure) that we need to vote.
Arnaud
On 1/26/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
>
> On 1/26/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> > It looks good to me, just two remarks:
> >
> > - did you test it with maven 1.0.2 and artif
Arnaud HERITIER wrote:
> Jason, in fact we're right ;-)
> These plugins are used in the bootstrap but they are downloaded from the
> remote repository instead of to be built before.
> I'll change that to build them during the bootstrap. It's anormal that we
> have to download them.
>
I think that
Arnaud HERITIER wrote:
>> Plugins to demote with work to do:
>>
>> [+1] repository - (do we need upload-bundle? I don't see where it's used)
>
>
> Carlos, Brett, are you sure that we can always use these bundles with the m2
> repo ?
> Do you continue to upload in the old m1 repository ?
>
yep.
On 1/26/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> It looks good to me, just two remarks:
>
> - did you test it with maven 1.0.2 and artifact plugin 1.5.2?
I am using 1.0.2 for the moment. So yes!
> - it would be good to have some simple test cases
Well ; OK, I just need to figure out which
It looks good to me, just two remarks:
- did you test it with maven 1.0.2 and artifact plugin 1.5.2?
- it would be good to have some simple test cases
I'd be +1 for moving it to the core plugins, do we have to do a vote for
that?
-Lukas
Stephane Nicoll wrote:
What about the source plugin?
What about the source plugin? I asked twice to review it and it will
be needed if we want a IDE-source integration in m1.
Thanks,
Stéphane
On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> I would like also to propose that we move to the sandbox these components
> that we don't use :
> - e
Jason, in fact we're right ;-)
These plugins are used in the bootstrap but they are downloaded from the
remote repository instead of to be built before.
I'll change that to build them during the bootstrap. It's anormal that we
have to download them.
arnaud
On 1/26/06, Arnaud HERITIER <[EMAIL PROT
Ok, I see what you mean now.
+1 to remove touchstone and touchstone-partner, if they are really unused.
-1 for examples, I think it can be useful to have some example templates
for illustration purpose (I think I used it once to point a user to).
-Lukas
Arnaud HERITIER wrote:
No, I'm right
No, I'm right :-)
All touchstone tests are in the core :
http://svn.apache.org/viewcvs.cgi/maven/maven-1/core/trunk/src/test/touchstone-build/
We don't use the plugins.
Arnaud
On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
> ouchhh
>
> I forgot it ;-)
>
> thx jason !
>
> arnaud
>
> On 1
ouchhh
I forgot it ;-)
thx jason !
arnaud
On 1/26/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> Arnaud HERITIER wrote:
> > I would like also to propose that we move to the sandbox these
> components
> > that we don't use :
> > - examples
>
> > - touchstone
> > - touchstone-partner
>
> These
Arnaud HERITIER wrote:
I would like also to propose that we move to the sandbox these components
that we don't use :
- examples
- touchstone
- touchstone-partner
These aren't used in the m1 bootstrap anymore?
WDYT ?
On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
Lukas, I forgot
I would like also to propose that we move to the sandbox these components
that we don't use :
- examples
- touchstone
- touchstone-partner
WDYT ?
On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
> Lukas, I forgot to say that I began to update this page :
> http://docs.codehaus.org/display
Lukas, I forgot to say that I began to update this page :
http://docs.codehaus.org/display/MAVEN/Maven+1.X+plugins
If you can take a look at it.
Arnaud
On 1/26/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
>
>
> On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> >
> > Hello again,
> >
> >
On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
>
> Hello again,
>
> We have discussed this before somewhat superficially but never got to a
> concrete conclusion so I'd like to call for a formal vote to finalize
> this and collect some opinions if necessary. Let me point out and
> emphasize t
> -Original Message-
> From: Lukas Theussl [mailto:[EMAIL PROTECTED]
> Sent: mardi 24 janvier 2006 23:18
> To: Maven Developers List
> Subject: Re: [vote] [m1] demote plugins
>
>
>
> > OK. Just assign the issue to me, I'll do it.
>
> Thanks!
> -Original Message-
> From: Lukas Theussl [mailto:[EMAIL PROTECTED]
> Sent: mardi 24 janvier 2006 20:27
> To: Maven Developers List
> Subject: [vote] [m1] demote plugins
>
> Hello again,
>
> We have discussed this before somewhat superficially but never got
Was this necessary, or just done for consistency?
Need to ask Arnaud about that.
You *have* to use the nsis plugin to do a Windows release of Maven.
Acknowledged, nsis will stay.
I agree with demoting jcoverage, thinking more about it.
:)
-Lukas
Lukas Theussl wrote:
> At least cruisecontrol and jcoverage have had some dependencies updated
> to match them with the maven core. So if we want to include them in
> m1.1, we have to re-release them.
Was this necessary, or just done for consistency?
> But as I said, my main concern is that I am
With the exception of nsis (which is required to release Maven!), the
current state is likely identical to the last release, so leaving them
as is seems fine.
At least cruisecontrol and jcoverage have had some dependencies updated
to match them with the maven core. So if we want to include th
Does this not still work? All it does it create bundles that people can
submit to JIRA.
Yes it works. As mentioned above, I will move it into artifact. OK?
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
Lukas Theussl wrote:
Hello again,
Plugins to demote with work to do:
[] repository - (do we need upload-bundle? I don't see where it's used)
Does this not still work? All it does it create bundles that people can
submit to JIRA.
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apa
Lukas Theussl wrote:
> Discussed that with Carlos, I will move the create-upload-bundle goal
> into the artifact plugin. OK?
I guess so.
> So you'd say we include the latest stable version or just re-release in
> the current state?
With the exception of nsis (which is required to release Maven!
[] repository - (do we need upload-bundle? I don't see where it's used)
don't we need to keep the bundle stuff?
Discussed that with Carlos, I will move the create-upload-bundle goal
into the artifact plugin. OK?
[] antlr
[] cruisecontrol
[] jcoverage - replaced by Cobertura
[] jdif
OK. Just assign the issue to me, I'll do it.
Thanks! I will open issues as soon as the vote is finalized.
Personally, +1. I am surprised to see the JBoss plugin there though.
Any contact with the JBoss people? (Maybe someone there can maintain
it)
No idea. Maybe Vincent M has some contact
Lukas Theussl wrote:
Last time I checked the the scm plugin used code from the release
plugin - the "release:transform" taglib.
That's why I said 'move used classes to SCM plugin'.
Sorry, missed that part :(
In M2 the pom transformation is handled by the release-plugin.
An alternative
Lukas Theussl wrote:
> Plugins to demote with work to do:
>
> [] repository - (do we need upload-bundle? I don't see where it's used)
don't we need to keep the bundle stuff?
> [] release - move used classes to SCM plugin (Fabrizio?)
+1
> [] j2ee - move the resolver tag into ear and j2ee:valida
On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> Hello again,
>
> [] j2ee - move the resolver tag into ear and j2ee:validate-war to
> war:validate (Stephane?)
OK. Just assign the issue to me, I'll do it.
> Other unmaintained plugins:
>
> [] abbot
> [] antlr
> [] castor - not working (see MP
Last time I checked the the scm plugin used code from the release plugin
- the "release:transform" taglib.
That's why I said 'move used classes to SCM plugin'.
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
Lukas Theussl wrote:
Carlos Sanchez wrote:
cruisecontrol: worked last time I tried it and I believe people use
it, and it's referenced by Vincent's book.
That means you take over maintanance? ;) There are 14 issues open for it
in Jira and someone has to go through them. Here is a quote from
I was just pointing out some info to take a better decision, let me update then
cruisecontrol: +1
release: if that functionality is moved to other place +1
repository: create-upload-bundle is used in the docs to create uploads
to ibiblio, not sure if it's in that plugin or not, but that
functionali
Carlos Sanchez wrote:
cruisecontrol: worked last time I tried it and I believe people use
it, and it's referenced by Vincent's book.
That means you take over maintanance? ;) There are 14 issues open for it
in Jira and someone has to go through them. Here is a quote from Brett,
replying to a
cruisecontrol: worked last time I tried it and I believe people use
it, and it's referenced by Vincent's book.
release: it was used for release:prepare and release:perfrom
repository: if upload-bundle is not create-upload-bundle i'm +1
+1 for everything else
On 1/24/06, Lukas Theussl <[EMAIL PROT
Hello again,
We have discussed this before somewhat superficially but never got to a
concrete conclusion so I'd like to call for a formal vote to finalize
this and collect some opinions if necessary. Let me point out and
emphasize that we are quite short of manpower for m1, so the main
motivat
34 matches
Mail list logo
