Sorry, I strongly disagree, dependency is not optional. If there were not a valid, higher resolution path, the build would fail as well.
Regards, Christophe -----Original Message----- From: Christian Schulte [mailto:c...@schulte.it] Sent: Freitag, 5. August 2016 16:33 To: Maven Developers List <dev@maven.apache.org> Subject: Re: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo Am 08/05/16 um 16:10 schrieb Thiebaud, Christophe: > ... oh ... I was 200% sure that parent did not allow a version range ... Introduced in Maven 3.2.2. Broken since a few releases. Fixed in 3.4.0-SNAPSHOT. > > I tried, -> BUILD SUCCESS. > > Hourah, and thanks. > > Let see now if this option is ok with our developers. > > In any case, don't you think there is some valid reason to fill a jira entry ? Issue is the repository being in an inconsistent state. It would not have been possible to deploy lib-1.0-SNAPSHOT without its parent being available in the repository. > I mean, iterating over a set of possible resolutions should not fail if one > of the set fails, but if no acceptable resolution is found at the end, no ? > > In fact, this is what happen when the (failing) parent relationship is > replaced with a (failing as well) dependency relationship. What exactly do you mean with "failing as well"? There is a difference between not finding a dependency and not finding a parent. The first is comparable to an "optional file not found" whereas the parent is nothing optional. Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
