You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Tom Davies <to...@atlassian.com> on 2007/08/29 03:14:15 UTC
Atlassian to bring Maven Clover plugin development in-house
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?)
Thanks,
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Arnaud HERITIER <ah...@gmail.com>.
+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 <jo...@gmail.com> wrote:
> On 8/30/07, Brett Porter <br...@apache.org> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by jallen <jo...@hotmail.com>.
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 <br...@apache.org> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Jochen Wiedmann <jo...@gmail.com>.
On 8/30/07, Brett Porter <br...@apache.org> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Emmanuel Venisse <em...@venisse.net>.
+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 <ja...@planet57.com> 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: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>> --
>> ..........................................................
>> 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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Grzegorz Kossakowski <gk...@apache.org>.
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
> <overrides>
> <override>
> <groupId>...
> <artifactId>...
> <version>[1.0; 3.0(...
> </override>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Jerome Lacoste <je...@gmail.com>.
On 8/30/07, Brett Porter <br...@apache.org> 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
<overrides>
<override>
<groupId>...
<artifactId>...
<version>[1.0; 3.0(...
</override>
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Atlassian to bring Maven Clover plugin development in-house
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
+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:brett@apache.org]
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 <ja...@planet57.com> 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: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> ..........................................................
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Stephane Nicoll <st...@gmail.com>.
Same here.
Stéphane
On 8/30/07, Jason Dillon <ja...@planet57.com> 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 <ja...@planet57.com> 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: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>
> >>>
> >>> --------------------------------------------------------------------
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> >>
> >>
> >> --
> >> ..........................................................
> >> 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: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Large Systems Suck: This rule is 100% transitive. If you build one,
you suck" -- S.Yegge
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Jason Dillon <ja...@planet57.com>.
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 <ja...@planet57.com> 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: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>> --
>> ..........................................................
>> 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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Vincent Siveton <vi...@gmail.com>.
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 <br...@apache.org>:
> 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 <ja...@planet57.com> 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: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
> > --
> > ..........................................................
> > 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: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Brett Porter <br...@apache.org>.
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 <ja...@planet57.com> 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: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> ..........................................................
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Arnaud HERITIER <ah...@gmail.com>.
We can move it in the sandbox (just to keep it visible) ?
Or in a deprecated area ?
Arnaud
On 30/08/2007, Jason Dillon <ja...@planet57.com> 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: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Jason Dillon <ja...@planet57.com>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Jason van Zyl <ja...@maven.org>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Brett Porter <br...@apache.org>.
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Atlassian to bring Maven Clover plugin development in-house
Posted by Jason van Zyl <ja...@maven.org>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org