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

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...

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