How to only resolve versions numbers and/or poms without downloading artifact Jars?

[binodpanta]

Hello ShrinkWrap devs/users, my first post here.

How do I resolve only poms, I don't want Shrinkwrap to download the jars for me, I am using this type of snippet, and my code gets runs over and over ni a large number of nodes, which is causing large network traffic, when all I want in this phase is to resolve the versions of things,

I am using this snippet,

MavenResolvedArtifact a = Maven.configureResolver() .withMavenCentralRepo(false) .fromClassloaderResource("downloader-settings.xml") .resolve(artifactGAV).withoutTransitivity() .asSingleResolvedArtifact();

I am doing this for a large number of components, and all I want is to resolve the latest version numbers of artifacts, I don't actually need to download them

[kpiwko]

Hi Binod,

this is not possible at this moment. However, it should not be that difficult to implement this - we just need to split collectAndResolve into two phases and implement API to access http://download.eclipse.org/aether/aether-core/0.9.0.M2/apidocs/org/eclipse/aether/RepositorySystem.html#collectDependen…. Can you please file a Feature Request at https://issues.jboss.org/browse/SHRINKRES ?

Thanks,

Karel

[binodpanta]

Thanks Karel for addressing this, I will file a help request. In the meantime, how easy might it be for me to get around this and maybe use Aether api directly, do you recommend that?

I was hoping there was a way to maybe use the resolution filters mechanism to only resolve poms, I am familiar with writing custom MavenStrategy and filters by now, so if there is such a way I can try that out

[binodpanta]

Also, I thought I would 'game the system' and try replacing all requests to use the 'pom' packaging type during resolution thinking it would give me just the poms, and it almost did except there is a line of code specifically blocking pom artifacts types fro getting into the output! right before this line runs, I do see that my pom artifacts are being found (which makes sense since the dependency plugni also allows me to only grab poms by adding 'type' pom to my dependency tags.

// apply post filtering

        return PostResolutionFilterApplicator.postFilter(resolvedArtifacts);

in my case it is almost as if I need the exact opposite filter, which only accepts poms or a way to override that filter, that I can inject from outside

// maybe something like this

        return PostResolutionFilterApplicator.postFilter(resolvedArtifacts, customPOMOnlyFilter);

Wooh, got close...

[kpiwko]

POMs are indeed removed from resulting set of resolved artifacts - due to fact the will interfere with resulting set, we are just using their dependencies. However, we should be able to use the same model and split collection (metadata only) and resolution (artifacts).

Could be like:

Maven.configureResolver().resolveOnlyMetadata().loadPomFromFile("pom.xml").importRuntimeDependencies()  .resolve().withTransitivity().as(MavenResolvedArtifact.class);

[binodpanta]

Thanks, I see that the issue says lined up for release 2.2.1-cr1

Is there anyway I can preview the fix? I am having a real need for this fix in my system, where things are taking very long times. When is the release for cr-1 expected? If it is going to take some more time, can I get instructions on how to get the latest build to start my prequals ?

Thanks

[kpiwko]

I don't want to promise anything but end of October could be reasonable target.

[sschuberth]

Is there any update on the availability of this feature?