+1 to remove them altogether instead of moving to the sandbox.
-Vincent
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 11 May 2004 01:39
> To: Maven Developers List ([EMAIL PROTECTED])
> Subject: [VOTE] plugin evictions
>
> I would like to move the codeswitch
+1 for both
#Arnaud
> -Message d'origine-
> De : Brett Porter [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 11 mai 2004 01:39
> À : Maven Developers List ([EMAIL PROTECTED])
> Objet : [VOTE] plugin evictions
>
> I would like to move the codeswitcher plugin maven-plugins-sandbox and out
> of
The perforce plugin supposedly just gets the jars onto the classpath.
I'm +1 on both.
--
dIon Gillard, Multitask Consulting
Brett Porter <[EMAIL PROTECTED]> wrote on 11/05/2004 09:39:14 AM:
> I would like to move the codeswitcher plugin maven-plugins-sandbox and
out
> of the Maven 1.0 release
On Tue, 11 May 2004 09:39:14 +1000, Brett Porter
<[EMAIL PROTECTED]> wrote:
I would like to move the codeswitcher plugin maven-plugins-sandbox and
out of the Maven 1.0 release as Jason has indicated it was experimental.
+1, experimental code shouldn't be in maven-plugins now that we have a
sandb
On Mon, 2004-05-10 at 19:39, Brett Porter wrote:
> I would like to move the codeswitcher plugin maven-plugins-sandbox and out
> of the Maven 1.0 release as Jason has indicated it was experimental.
>
> I would also like to delete the perforce plugin as it appears to me to do
> nothing.
+1 To nukin
