On 3/4/07, Kenney Westerhof <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
