You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@sonatype.com> on 2009/12/27 22:11:34 UTC
Artifact Resolution code in 2.x
Is anyone planning on actually doing any bug fixing in the 2.x artifact resolution code?
Lots of this stuff has been fixed in 3.x and I was just going to push any bugs I saw in JIRA to 3.x and validate as fixed and for the ones that aren't schedule them to be fixed.
I don't think at this point anyone really wants to muck around in the 2.x codebase, but if someone wants to then I will leave the issues alone in JIRA.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Artifact Resolution code in 2.x
Posted by Brian Fox <br...@infinity.nu>.
Lol, I can't imagine anyone diving into the 2.x resolution code again.
Punt them to 3.x
On Mon, Dec 28, 2009 at 8:22 PM, Jason van Zyl <ja...@sonatype.com> wrote:
> Then anything I see I will just move to 3.x because I honestly don't think anyone is going to fix them in 2.x and the code is too different now to backport any of it.
>
> On 2009-12-28, at 8:13 PM, Brett Porter wrote:
>
>> If they are fixed in 3.x, it'd be good to just close them out. Ideally, point them at the issue that resolves them though as superceded / duplicate. Folks will keep coming across them at a later date searching for something in the 2.x line.
>>
>> - Brett
>>
>> On 28/12/2009, at 8:11 AM, Jason van Zyl wrote:
>>
>>> Is anyone planning on actually doing any bug fixing in the 2.x artifact resolution code?
>>>
>>> Lots of this stuff has been fixed in 3.x and I was just going to push any bugs I saw in JIRA to 3.x and validate as fixed and for the ones that aren't schedule them to be fixed.
>>>
>>> I don't think at this point anyone really wants to muck around in the 2.x codebase, but if someone wants to then I will leave the issues alone in JIRA.
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ----------------------------------------------------------
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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, Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> 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: Artifact Resolution code in 2.x
Posted by Jason van Zyl <ja...@sonatype.com>.
Then anything I see I will just move to 3.x because I honestly don't think anyone is going to fix them in 2.x and the code is too different now to backport any of it.
On 2009-12-28, at 8:13 PM, Brett Porter wrote:
> If they are fixed in 3.x, it'd be good to just close them out. Ideally, point them at the issue that resolves them though as superceded / duplicate. Folks will keep coming across them at a later date searching for something in the 2.x line.
>
> - Brett
>
> On 28/12/2009, at 8:11 AM, Jason van Zyl wrote:
>
>> Is anyone planning on actually doing any bug fixing in the 2.x artifact resolution code?
>>
>> Lots of this stuff has been fixed in 3.x and I was just going to push any bugs I saw in JIRA to 3.x and validate as fixed and for the ones that aren't schedule them to be fixed.
>>
>> I don't think at this point anyone really wants to muck around in the 2.x codebase, but if someone wants to then I will leave the issues alone in JIRA.
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ----------------------------------------------------------
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
>
>
>
>
>
> ---------------------------------------------------------------------
> 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, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Artifact Resolution code in 2.x
Posted by Brett Porter <br...@apache.org>.
If they are fixed in 3.x, it'd be good to just close them out. Ideally, point them at the issue that resolves them though as superceded / duplicate. Folks will keep coming across them at a later date searching for something in the 2.x line.
- Brett
On 28/12/2009, at 8:11 AM, Jason van Zyl wrote:
> Is anyone planning on actually doing any bug fixing in the 2.x artifact resolution code?
>
> Lots of this stuff has been fixed in 3.x and I was just going to push any bugs I saw in JIRA to 3.x and validate as fixed and for the ones that aren't schedule them to be fixed.
>
> I don't think at this point anyone really wants to muck around in the 2.x codebase, but if someone wants to then I will leave the issues alone in JIRA.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org