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...@maven.org> on 2007/03/03 20:09:24 UTC
Being careful with backward compat
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Being careful with backward compat
Posted by Brett Porter <br...@apache.org>.
Ok. I'll take a look at what the assembly plugin does and write a doc
on plugin testing before I start with the surefire plugin.
- Brett
On 06/03/2007, at 5:55 AM, Brian E. Fox wrote:
> 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:brett@apache.org]
> 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:jason@maven.org]
>> 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 <ja...@maven.org> 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: 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
>
>
> ---------------------------------------------------------------------
> 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: Being careful with backward compat
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:brett@apache.org]
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:jason@maven.org]
> 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 <ja...@maven.org> 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: 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
---------------------------------------------------------------------
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: Being careful with backward compat
Posted by Brett Porter <br...@apache.org>.
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:jason@maven.org]
> 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 <ja...@maven.org> 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: 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Being careful with backward compat
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:jason@maven.org]
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 <ja...@maven.org> 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: 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: Being careful with backward compat
Posted by Jason van Zyl <ja...@maven.org>.
On 4 Mar 07, at 11:21 PM 4 Mar 07, Jerome Lacoste wrote:
> On 3/4/07, Kenney Westerhof <ke...@apache.org> wrote:
>>
>>
>> Jason van Zyl wrote:
>> >
>> > 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.
>> >
>>
>> Just to stress the importance of the integration tests: surefire
>> depends
>> on plexus-utils 1.1, but that is NOT the version it's running against
>> as currently maven's plexus-utils is used. Up till now this
>> version matched,
>> but other plugins (like release) require newer versions of p-u.
>>
>> Also, most plugins depend on maven-* 2.0; again the actual version
>> used
>> depends on the maven installation. For these artifacts, clirr or
>> jdiff
>> would be appropriate, but again, integration tests against all
>> released
>> maven versions is necessary.
>
> Hi,
>
> the fact that maven uses its internal plexus-utils has bitten me
> several times.
>
> I have several issues today that are blocked because maven depends on
> a buggy plexus-utils.
>
> Could we find a solution to that problem?
I am looking at a few options, but I'm working with Torsten's very
cool minijar plugin and I think by the end of the day I will have a
way to hide plexus-utils internal use in the Maven core from any
plugin that use it. It employs some static rewriting of the version
that Maven's core uses internally which means that each plugin will
be able to load its own version of plexus-utils. Another option is a
change to classworlds to have export filters to match its import
filters. I might add this anyway but I'm trying the minijar method
first.
>
> One idea is to copy all classes of plexus-utils and move them into a
> separate cloned library that sits in its own namespace.
We have done that in the past and if what I'm doing with minijar
doesn't work in short order then I believe that's what should be done
with surefire so we don't wreak havoc with the release of 2.0.6 and
2.1-alpha-1.
>
> e.g. org.apache.maven.plexus.utils
>
> Each time the library has to be updated, rinse and re-clone.
>
Yup, not elegant but it will certainly work. Certainly better then
hosing everyone.
Jason.
> J
>
> ---------------------------------------------------------------------
> 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: Being careful with backward compat
Posted by Jerome Lacoste <je...@gmail.com>.
On 3/4/07, Kenney Westerhof <ke...@apache.org> wrote:
>
>
> Jason van Zyl wrote:
> >
> > 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.
> >
>
> Just to stress the importance of the integration tests: surefire depends
> on plexus-utils 1.1, but that is NOT the version it's running against
> as currently maven's plexus-utils is used. Up till now this version matched,
> but other plugins (like release) require newer versions of p-u.
>
> Also, most plugins depend on maven-* 2.0; again the actual version used
> depends on the maven installation. For these artifacts, clirr or jdiff
> would be appropriate, but again, integration tests against all released
> maven versions is necessary.
Hi,
the fact that maven uses its internal plexus-utils has bitten me several times.
I have several issues today that are blocked because maven depends on
a buggy plexus-utils.
Could we find a solution to that problem?
One idea is to copy all classes of plexus-utils and move them into a
separate cloned library that sits in its own namespace.
e.g. org.apache.maven.plexus.utils
Each time the library has to be updated, rinse and re-clone.
J
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Being careful with backward compat
Posted by Kenney Westerhof <ke...@apache.org>.
Jason van Zyl wrote:
>
> 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.
>
Just to stress the importance of the integration tests: surefire depends
on plexus-utils 1.1, but that is NOT the version it's running against
as currently maven's plexus-utils is used. Up till now this version matched,
but other plugins (like release) require newer versions of p-u.
Also, most plugins depend on maven-* 2.0; again the actual version used
depends on the maven installation. For these artifacts, clirr or jdiff
would be appropriate, but again, integration tests against all released
maven versions is necessary.
-- Kenney
>> 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 <ja...@maven.org> 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: 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: Being careful with backward compat
Posted by Jason van Zyl <ja...@maven.org>.
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 <ja...@maven.org> 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: 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: Being careful with backward compat
Posted by Arnaud HERITIER <ah...@gmail.com>.
Jason,
Couldn't we enforce the usage of something like jdiff to check if there's
an incompatibility between releases.
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.
Arnaud
On 3/3/07, Jason van Zyl <ja...@maven.org> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>