Here:
00:18] BrianFox: btw, is it me or are the assembly IT's pretty screwed?
[00:18] BrianFox: i see that it depends on the plug-it-plugin in sandbox
but it doesn't even compile right now
[00:20] brett: not tried, wouldn't doubt it
[00:21] brett: I'm just writing up mails about this sort of topic. We
have big problems with testing, documentation, and other general stuff
like that.

[00:27] BrianFox: heh. i tried upgrading archiver and that somehow
caused massive failures in the testing harness so I'm about at a dead
end soon.
[00:28] BrianFox: something about plexus container.setup() doesn't exist
anymore
[00:28] brett: probably because that dragged in a new, incompatible
version of the plexus container

-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 06, 2007 2:28 AM
To: Maven Developers List
Subject: Re: Being careful with backward compat

I can't find or recall this - do you have a log/date?

- Brett

On 05/03/2007, at 7:46 AM, Brian E. Fox wrote:

> The lates plexus-utils blows up the testing harness too because it
> changes some of the core classes. I don't remember the exact  
> compilation
> error, but I discussed with Brett on IRC.
>
>
> -----Original Message-----
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 03, 2007 5:31 PM
> To: Maven Developers List
> Subject: Re: Being careful with backward compat
>
>
> On 3 Mar 07, at 4:57 PM 3 Mar 07, Arnaud HERITIER wrote:
>
>> Jason,
>>
>>  Couldn't we enforce the usage of something like jdiff to check if
>> there's an incompatibility between releases.
>
> Yup, we could use that or Clirr as Vincent suggested. That's one  
> part of
> the answer. The separate integration tests are another part and we'll
> get there. The plugins released need to be exercised against released
> and upcoming versions.
>
>>  It something that we already had (incompatibility of m1 plugins with
>> m1.0.x whereas m1.1 isn't released) and which is really damaging for
>> our community.
>
> Yes, I think Torsten's awesome minijar plugin is going to be very  
> handy.
> I'm about to check into trunk some plugin configurations which will  
> hide
> some common dependencies which cause problems. Plexus Utils being  
> one of
> them.
>
> Jason.
>
>>
>> Arnaud
>>
>> On 3/3/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi,
>>>
>>> The current release of the Surefire plugin is a bit a nightmare with
>>> respect to backward compatibility. The problem is incompatible
>>> changes made to plexus-utils. The most current release will work  
>>> with
>>> 2.0.5 because it still uses plexus-utils 1.1 but with the upgraded
>>> plexus-utils in trunk in fork mode will make it blow up. I'm trying
>>> to fix this now as in fork mode the branch and trunk now fail  
>>> because
>>> 1.1 and 1.4 of plexus utils have changes in the command line  
>>> classes.
>>> I am doing some magic with Torsten's Minijar plugin on the trunk,  
>>> but
>
>>> for the branch I don't know if we want to employ this but with
>>> plexus-
>>> utils 1.4 there now we're going screw everyone. John and Kenney
>>> chatted about it briefly but we probably want to address this  
>>> quickly
>
>>> and in a new release of surefire.
>>>
>>> Thanks,
>>>
>>> Jason.
>>>
>>>
>>>
>>> --------------------------------------------------------------------

>>> -
>>> 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]


---------------------------------------------------------------------
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]

Reply via email to