Wrong list, I presume. -Rahul
On 1/8/08, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: > 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
