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: [email protected] For additional commands, e-mail: [email protected]
