commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann" <jochen.wiedm...@gmail.com>
Subject Request help on MCLIRR-7
Date Tue, 08 Jan 2008 21:52:04 GMT
Hi,

I have evaluated the bug report MCLIRR-7 and must admit that I am
stuck. Here's what I have found:

Clirr requires two classloaders, one with the previous version and one
with the current version. In order to create the first classloader,
the clirr-maven-plugin does the following:

- Resolves an artifact from the repositories. (For example
commons-fileupload-1.2.)
- Invokes the following snipped with the artifact:

    // TODO: better way? Can't use previousArtifact as the
originatingArtifact, it culls everything out
    // perhaps resolve the artifact itself (not the pom artifact),
then load the pom and get dependencies
    Artifact dummy = factory.createProjectArtifact( "dummy", "dummy", "1.0" );
    ArtifactResolutionResult result = resolver.resolveTransitively(
previousArtifacts,
            dummy, localRepository, project.getRemoteArtifactRepositories(),
            metadataSource, null );

The problem is that the result doesn't contain any artifacts, not even
the "previous version" artifact, which is in the previousArtifacts
collection.

Any idea what's wrong or what I might try instead?


Thanks,

Jochen


-- 
Look, that's why there's rules, understand? So that you think before
you break 'em.

    -- (Terry Pratchett, Thief of Time)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message