RE: Atlassian to bring Maven Clover plugin development in-house
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/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 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 automatically detect that the plugin has now moved somewhere else? I am not sure how this would fit with the current implementation and the implicit location of the packages on the remote repositories. As maven searches in the old location, there would need to be some sort of link from the old to the new, which somewhat inverts the dependency between the superseder and deprecated as used in the deb format. Maybe a feature to implement in the repository manager, using some sort of ... ... [1.0; 3.0(... in the overriding POM and some backlinks added by the repo manager when the overriding POM is added to the repository ? I would love maven to tell me: warning this dependency is obsolete. Cheers, Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 > > original place) would get my vote. > > +1 for retired > > 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 automatically detect that the plugin has now moved > somewhere else? I am not sure how this would fit with the current > implementation and the implicit location of the packages on the remote > repositories. As maven searches in the old location, there would need > to be some sort of link from the old to the new, which somewhat > inverts the dependency between the superseder and deprecated as used > in the deb format. > > Maybe a feature to implement in the repository manager, using some sort of > > > ... > ... > [1.0; 3.0(... > > in the overriding POM > > and some backlinks added by the repo manager when the overriding POM > is added to the repository ? > > I would love maven to tell me: warning this dependency is obsolete. > > Cheers, > > Jerome > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 hosted in Atlassian's public svn repository. Many thanks to Vincent Massol and others for their work on this plugin! Thanks. I'm happy to see someone taking care of this baby since I've not been very active on it lately and there are several patches and user request in JIRA for it. Let me know if there's anything I can do to help. -Vincent I have questions about the best way to make this transition -- should we release a final version of the plugin with the existing org.apache.maven.plugins groupId which outputs a message explaining the change? What have other people done when a plugin changes groupId? (and would these questions be better asked on the user list rather than here?) Thanks, Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 automatically detect that the plugin has now moved > somewhere else? I am not sure how this would fit with the current > implementation and the implicit location of the packages on the remote > repositories. As maven searches in the old location, there would need > to be some sort of link from the old to the new, which somewhat > inverts the dependency between the superseder and deprecated as used > in the deb format. > > Maybe a feature to implement in the repository manager, using some sort of > > > ... > ... > [1.0; 3.0(... > > in the overriding POM > > and some backlinks added by the repo manager when the overriding POM > is added to the repository ? > > I would love maven to tell me: warning this dependency is obsolete. +1000 for this proposal in general. I won't comment technical details as I'm not so much involved in Maven internals. Nevertheless, such option would allow much smoother migration from poorly chosen groupIds and artifactIds as well. -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 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 automatically detect that the plugin has now moved somewhere else? I am not sure how this would fit with the current implementation and the implicit location of the packages on the remote repositories. As maven searches in the old location, there would need to be some sort of link from the old to the new, which somewhat inverts the dependency between the superseder and deprecated as used in the deb format. Maybe a feature to implement in the repository manager, using some sort of ... ... [1.0; 3.0(... in the overriding POM and some backlinks added by the repo manager when the overriding POM is added to the repository ? I would love maven to tell me: warning this dependency is obsolete. Cheers, Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Atlassian to bring Maven Clover plugin development in-house
+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-house 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 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 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, 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 be much activity here, and I'd prefer to >>> avoid confusion. Should we retire the code (though obviously keep >>> it around for anyone that might want it for some reason), and close >>> the JIRA once this out? >>> >>> Or should we continue to maintain the current plugin, stating >>> clearly somewhere that it's for Clover 1 only? >>> >>> - Brett >>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > .. > Arnaud HERITIER > .. > OCTO Technology - aheritier AT octo DOT com > www.octo.com | blog.octo.com > .. > ASF - aheritier AT apache DOT org > www.apache.org | maven.apache.org > ... > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 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 under penalty of law, resulting in > a preventative effect against manipulating elections. > > The german government justifying the use of electronic voting machines > and obviously believing that we don't need a police, because all > illegal actions are forbidden. > > http://dip.bundestag.de/btd/16/051/1605194.pdf > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Atlassian-to-bring-Maven-Clover-plugin-development-in-house-tf4345201s177.html#a12404487 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 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 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 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, 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 be much activity here, and I'd prefer to > >>> avoid confusion. Should we retire the code (though obviously keep > >>> it around for anyone that might want it for some reason), and close > >>> the JIRA once this out? > >>> > >>> Or should we continue to maintain the current plugin, stating > >>> clearly somewhere that it's for Clover 1 only? > >>> > >>> - Brett > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > -- > > .. > > Arnaud HERITIER > > .. > > OCTO Technology - aheritier AT octo DOT com > > www.octo.com | blog.octo.com > > .. > > ASF - aheritier AT apache DOT org > > www.apache.org | maven.apache.org > > ... > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HELP was Re: Atlassian to bring Maven Clover plugin development in-house
Hi, 1) this not the good list. You can ask help on the users one 2) it's a bad practice to continue a thread with another not related question 3) You can read docs : - http://maven.apache.org - free books are available on devzuz.com and sonatype.com Arnaud On 30/08/2007, Pattabiraman, Venkatraman <[EMAIL PROTECTED]> wrote: > Hi > > I'm new to Maven. I don't know where to start. I have set the path of Maven. > > I have already created the package strutcture in eclipse. I have also plugged > in the maven in eclipse. > > From here i 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 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 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]> 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 under penalty of law, resulting in > > a preventative effect against manipulating elections. > > > > The german government justifying the use of electronic voting machines > > and obviously believing that we don't need a police, because all > > illegal actions are forbidden. > > > > http://dip.bundestag.de/btd/16/051/1605194.pdf > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > .. > Arnaud HERITIER > .. > OCTO Technology - aheritier AT octo DOT com > www.octo.com | blog.octo.com > .. > ASF - aheritier AT apache DOT org > www.apache.org | maven.apache.org > ... > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be copied, > disclosed to, retained or used by, any other party. If you are not an > intended recipient then please promptly delete this e-mail and any attachment > and all copies and inform the sender. Thank you. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
On 8/30/07, Pattabiraman, Venkatraman <[EMAIL PROTECTED]> wrote: > Hi > > I'm new to Maven. I don't know where to start. I have set the path of Maven. You're probably new to the Internet as well :) User question -> user list and please don't hack another thread for your questions. Thanks, Stéphane > > I have already created the package strutcture in eclipse. I have also plugged > in the maven in eclipse. > > From here i 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 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 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]> 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 under penalty of law, resulting in > > a preventative effect against manipulating elections. > > > > The german government justifying the use of electronic voting machines > > and obviously believing that we don't need a police, because all > > illegal actions are forbidden. > > > > http://dip.bundestag.de/btd/16/051/1605194.pdf > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > .. > Arnaud HERITIER > .. > OCTO Technology - aheritier AT octo DOT com > www.octo.com | blog.octo.com > .. > ASF - aheritier AT apache DOT org > www.apache.org | maven.apache.org > ... > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be copied, > disclosed to, retained or used by, any other party. If you are not an > intended recipient then please promptly delete this e-mail and any attachment > and all copies and inform the sender. Thank you. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Atlassian to bring Maven Clover plugin development in-house
Hi I'm new to Maven. I don't know where to start. I have set the path of Maven. I have already created the package strutcture in eclipse. I have also plugged in the maven in eclipse. From here i 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 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 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]> 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 under penalty of law, resulting in > a preventative effect against manipulating elections. > > The german government justifying the use of electronic voting machines > and obviously believing that we don't need a police, because all > illegal actions are forbidden. > > http://dip.bundestag.de/btd/16/051/1605194.pdf > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 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]> 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 under penalty of law, resulting in > a preventative effect against manipulating elections. > > The german government justifying the use of electronic voting machines > and obviously believing that we don't need a police, because all > illegal actions are forbidden. > > http://dip.bundestag.de/btd/16/051/1605194.pdf > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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/* (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 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 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, 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 be much activity here, and I'd prefer to > avoid confusion. Should we retire the code (though obviously keep > it around for anyone that might want it for some reason), and close > the JIRA once this out? > > Or should we continue to maintain the current plugin, stating > clearly somewhere that it's for Clover 1 only? > > - Brett > > --- > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > >>> > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >> > >> > >> -- > >> .. > >> Arnaud HERITIER > >> .. > >> OCTO Technology - aheritier AT octo DOT com > >> www.octo.com | blog.octo.com > >> .. > >> ASF - aheritier AT apache DOT org > >> www.apache.org | maven.apache.org > >> ... > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
+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 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 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, 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 be much activity here, and I'd prefer to avoid confusion. Should we retire the code (though obviously keep it around for anyone that might want it for some reason), and close the JIRA once this out? Or should we continue to maintain the current plugin, stating clearly somewhere that it's for Clover 1 only? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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, at 4:31 PM, Arnaud HERITIER wrote: 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 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, 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 be much activity here, and I'd prefer to avoid confusion. Should we retire the code (though obviously keep it around for anyone that might want it for some reason), and close the JIRA once this out? Or should we continue to maintain the current plugin, stating clearly somewhere that it's for Clover 1 only? - Brett --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 under penalty of law, resulting in a preventative effect against manipulating elections. The german government justifying the use of electronic voting machines and obviously believing that we don't need a police, because all illegal actions are forbidden. http://dip.bundestag.de/btd/16/051/1605194.pdf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 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 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, 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 be much activity here, and I'd prefer to avoid confusion. Should we retire the code (though obviously keep it around for anyone that might want it for some reason), and close the JIRA once this out? Or should we continue to maintain the current plugin, stating clearly somewhere that it's for Clover 1 only? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 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, 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 be much activity here, and I'd prefer to > > avoid confusion. Should we retire the code (though obviously keep > > it around for anyone that might want it for some reason), and close > > the JIRA once this out? > > > > Or should we continue to maintain the current plugin, stating > > clearly somewhere that it's for Clover 1 only? > > > > - Brett > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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, 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 be much activity here, and I'd prefer to avoid confusion. Should we retire the code (though obviously keep it around for anyone that might want it for some reason), and close the JIRA once this out? Or should we continue to maintain the current plugin, stating clearly somewhere that it's for Clover 1 only? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 whatever they want to use it for. I don't expect there to be much activity here, and I'd prefer to avoid confusion. Should we retire the code (though obviously keep it around for anyone that might want it for some reason), and close the JIRA once this out? We definitely need to keep the code around as we have no idea whose done what with it. It's not unlikely it's been forked for whatever reason so we shouldn't remove it. The JIRA issues can be transfered to Atlassian. Or should we continue to maintain the current plugin, stating clearly somewhere that it's for Clover 1 only? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 be much activity here, and I'd prefer to avoid confusion. Should we retire the code (though obviously keep it around for anyone that might want it for some reason), and close the JIRA once this out? Or should we continue to maintain the current plugin, stating clearly somewhere that it's for Clover 1 only? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Atlassian to bring Maven Clover plugin development in-house
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 hosted in Atlassian's public svn repository. Many thanks to Vincent Massol and others for their work on this plugin! I have questions about the best way to make this transition -- should we release a final version of the plugin with the existing org.apache.maven.plugins groupId which outputs a message explaining the change? What have other people done when a plugin changes groupId? (and would these questions be better asked on the user list rather than here?) 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. Thanks, Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
