Re: [aether-users] resolving a POM with systemPaths

[Michael Guymon <michael.guymon@xxxxxxxxx>]

On 12/02/2011 06:27 PM, Benjamin Bentmann wrote:
> Furthermore, the handling of POMs is black and white, they are either 
> valid and allow retrieval of all declared dependencies or are invalid 
> and prevent retrieval of any declared dependency. I.e. there is no 
> best effort/guessing to extract some dependency information and 
> navigate around broken bits. As such your test cannot expect to get 
> logback etc. out of this invalid POM.
Ah, this is the crux of the matter. I assumed it was possible to 
continue resolution after stumbling upon an invalid systemPath. I think 
it you commented about this in an earlier post, but I thought you were 
pointing out the divergence of behavior between how Maven operates and 
what I am attempting.

> As explained before, if you want to get those dependencies, you would 
> have to make the maven-aether-provider consider the POM valid by 
> providing the missing project.basedir property.
Between manually setting the project.basedir property and the 
DependencySelector, I should be able to build a solution to my issue.

Sorry for burning your time looking at a pointless test!

thanks,
Michael