RE: Atlassian to bring Maven Clover plugin development in-house

2007-09-14 Thread Brian E. Fox
The consensus seemed to be to move clover to /retired. This is now done. -Original Message- From: Jerome Lacoste [mailto:[EMAIL PROTECTED] Sent: Thursday, August 30, 2007 11:14 AM To: Maven Developers List Subject: Re: Atlassian to bring Maven Clover plugin development in-house On 8/30

Re: Atlassian to bring Maven Clover plugin development in-house

2007-09-14 Thread Carlos Sanchez
see http://jira.codehaus.org/browse/MNG-2316 On 8/30/07, Jerome Lacoste <[EMAIL PROTECTED]> wrote: > On 8/30/07, Brett Porter <[EMAIL PROTECTED]> wrote: > > Yeah, we should do the same with the recently departed antlr plugin > > too. Move trunk to /retired/* (original tags would remain in the > >

Re: Atlassian to bring Maven Clover plugin development in-house

2007-09-14 Thread Vincent Massol
Hi Tom, On Aug 29, 2007, at 3:14 AM, Tom Davies wrote: Hi All, One consequence of Cenqua's acquisition by Atlassian is that we now have the resources to continue development of the Maven Clover plugin ourselves. It will remain open source under the Apache licence, and the source will be

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Grzegorz Kossakowski
Jerome Lacoste pisze: > On the Debian package management system (and probably in others) > there's a way to define a package as providing another package's > functionality, allowing superseding of information. > > Could there be a somewhat identical feature in maven which would > enable it to auto

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Jerome Lacoste
On 8/30/07, Brett Porter <[EMAIL PROTECTED]> wrote: > Yeah, we should do the same with the recently departed antlr plugin > too. Move trunk to /retired/* (original tags would remain in the > original place) would get my vote. +1 for retired On the Debian package management system (and probably in

RE: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Brian E. Fox
+1. I'd prefer to not have to look at them anymore so moving them out is a good idea. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, August 30, 2007 2:38 AM To: Maven Developers List Subject: Re: Atlassian to bring Maven Clover plugin development in-

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread jallen
retired is good for me too. So now i can pester the Cenqua guys about features for both the Eclipse plugin AND the maven plugin. wonderful ;) John Allen Jochen Wiedmann wrote: > > On 8/30/07, Brett Porter <[EMAIL PROTECTED]> wrote: > >> Yeah, we should do the same with the recently departed a

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Vincent Siveton
IMHO keep the maven-clover-plugin in its actual place is enough to preserve history. We just need to remove the stuff and add a README.TXT which gives the new SVN url. Have a look to the maven-antlr-plugin dir. Cheers, Vincent 2007/8/30, Brett Porter <[EMAIL PROTECTED]>: > Yeah, we should do the

HELP was Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Arnaud HERITIER
don't know how to start. > > can anybody help. > > venkat > > -Original Message- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 30, 2007 1:11 PM > To: Maven Developers List > Subject: Re: Atlassian to bring Maven Clover plugin develo

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Stephane Nicoll
gt; From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 30, 2007 1:11 PM > To: Maven Developers List > Subject: Re: Atlassian to bring Maven Clover plugin development in-house > > > +1 for a retired zone. > I think we'll have to wait a first release of

RE: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Pattabiraman, Venkatraman
-- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Thursday, August 30, 2007 1:11 PM To: Maven Developers List Subject: Re: Atlassian to bring Maven Clover plugin development in-house +1 for a retired zone. I think we'll have to wait a first release of the plugin by atlassian. We'll u

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Arnaud HERITIER
+1 for a retired zone. I think we'll have to wait a first release of the plugin by atlassian. We'll update the plugins list in the site and we'll move the svn code. Same thing for antlr. Arnaud On 30/08/2007, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: > On 8/30/07, Brett Porter <[EMAIL PROTECTED]

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Stephane Nicoll
Same here. Stéphane On 8/30/07, Jason Dillon <[EMAIL PROTECTED]> wrote: > Ya, retired/* sounds like a good place. > > --jason > > > On Aug 29, 2007, at 11:37 PM, Brett Porter wrote: > > > Yeah, we should do the same with the recently departed antlr plugin > > too. Move trunk to /retired/* (origin

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Emmanuel Venisse
+1 Emmanuel Brett Porter a écrit : Yeah, we should do the same with the recently departed antlr plugin too. Move trunk to /retired/* (original tags would remain in the original place) would get my vote. - Brett On 30/08/2007, at 4:31 PM, Arnaud HERITIER wrote: We can move it in the sandbo

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-30 Thread Jason Dillon
Ya, retired/* sounds like a good place. --jason On Aug 29, 2007, at 11:37 PM, Brett Porter wrote: Yeah, we should do the same with the recently departed antlr plugin too. Move trunk to /retired/* (original tags would remain in the original place) would get my vote. - Brett On 30/08/2007

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-29 Thread Jochen Wiedmann
On 8/30/07, Brett Porter <[EMAIL PROTECTED]> wrote: > Yeah, we should do the same with the recently departed antlr plugin > too. Move trunk to /retired/* (original tags would remain in the > original place) would get my vote. Sounds better than sandbox. -- "Besides, manipulating elections is un

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-29 Thread Brett Porter
Yeah, we should do the same with the recently departed antlr plugin too. Move trunk to /retired/* (original tags would remain in the original place) would get my vote. - Brett On 30/08/2007, at 4:31 PM, Arnaud HERITIER wrote: We can move it in the sandbox (just to keep it visible) ? Or in

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-29 Thread Arnaud HERITIER
We can move it in the sandbox (just to keep it visible) ? Or in a deprecated area ? Arnaud On 30/08/2007, Jason Dillon <[EMAIL PROTECTED]> wrote: > Its always gonna be in svn, so I'd just nuke it and if anyone wants > to find the old stuff they can dig it up. > > --jason > > > On Aug 29, 2007, at

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-29 Thread Jason Dillon
Its always gonna be in svn, so I'd just nuke it and if anyone wants to find the old stuff they can dig it up. --jason On Aug 29, 2007, at 8:07 PM, Brett Porter wrote: On 30/08/2007, at 3:01 AM, Jason van Zyl wrote: You can fork the code, and change the groupId. People will use yours, m

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-29 Thread Jason van Zyl
On 29 Aug 07, at 8:07 PM 29 Aug 07, Brett Porter wrote: On 30/08/2007, at 3:01 AM, Jason van Zyl wrote: You can fork the code, and change the groupId. People will use yours, most likely, by virtue of you developing it, but we'll leave the code here for anyone who wants to use it for what

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-29 Thread Brett Porter
On 30/08/2007, at 3:01 AM, Jason van Zyl wrote: You can fork the code, and change the groupId. People will use yours, most likely, by virtue of you developing it, but we'll leave the code here for anyone who wants to use it for whatever they want to use it for. I don't expect there to b

Re: Atlassian to bring Maven Clover plugin development in-house

2007-08-29 Thread Jason van Zyl
On 28 Aug 07, at 6:14 PM 28 Aug 07, Tom Davies wrote: Hi All, One consequence of Cenqua's acquisition by Atlassian is that we now have the resources to continue development of the Maven Clover plugin ourselves. It will remain open source under the Apache licence, and the source will be h