Am 08/05/16 um 13:27 schrieb Thiebaud, Christophe: > Reading Aether documentation : > > https://wiki.eclipse.org/Aether/Transitive_Dependency_Resolution > > looks that aether has been thought to manage this kind of issue: > > « For each direct dependency, a dependency selector is given a chance to > exclude the dependency from the graph » > > Any hint if and how it is possible to configure aether to ignore 'lib' > 0.0.1-SNAPSHOT when resolving the version range ?
I am a bit confused about the different error message right now. When it comes to version ranges, Aether reads all POMs of all versions it finds. If a parent has disappeared, it will fail building that model. Is there a way for you to purge the repository in a way not leaving broken projects around? I think that is the real issue. You would need some kind of index for this so that you can purge snapshots in a consistent way. Regarding the 'DependencySelector'. There currently is no way to change that. It's only used during initialization and I think that would be the wrong way of doing it <https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-aether-provider/src/main/java/org/apache/maven/repository/internal/MavenRepositorySystemUtils.java;h=877c27777bb4b102434aec64f4983932bcb64b5e;hb=HEAD#l104>. Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
