Re: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

Got it! Thanks. The dependency without [] needs to exist, but may not end up being used due to conflicts. Fair enough. :-) On Sat, Aug 6, 2016 at 3:24 PM, Christian Schulte wrote: > Am 08/06/16 um 05:15 schrieb Christian Schulte: > > It just takes the highest version the

Re: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

Am 08/06/16 um 05:15 schrieb Christian Schulte: > It just takes the highest version the version range resolver returns and uses > that or fails if nothing like that is available. If using version range syntax. - To

Re: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

Am 08/06/16 um 02:04 schrieb Fred Cooke: > A parent, I thought, used to be equivalent to [], ie, hard requirement. A > dependency without [] is NOT a hard requirement, simply advisory. So yeah, > they're different, or were. I wonder what semantics the ranged parents > behaviour has for a simple

Re: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

A parent, I thought, used to be equivalent to [], ie, hard requirement. A dependency without [] is NOT a hard requirement, simply advisory. So yeah, they're different, or were. I wonder what semantics the ranged parents behaviour has for a simple backward compatible (or not) plain version?

RE: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

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

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

RE: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

... oh ... I was 200% sure that parent did not allow a version range ... 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 ? I mean, iterating over a set of possible

Re: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

You maybe also could overcome this by using parent version ranges. 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: > >

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

RE: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

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

RE: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

Hi Christian, Thanks for the hint to try maven 3.4.0-SNAPSHOT I tried, and the result is again BUILD FAILURE - but with a nice colored system out, and - more seriously - a different, and IMHO misleading, error message. (Cf. full reproducible commands at

Re: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

Am 08/04/16 um 12:36 schrieb Thiebaud, Christophe: > I understand that pom file of lib 0.0.1-SNAPSHOT dependency cannot be built > because of missing (evicted) parent 0.0.1-SNAPSHOT. > > The point is that failing to build lib 0.0.1-SNAPSHOT pom file should not > result in a app failed build, as

RE: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

I understand that pom file of lib 0.0.1-SNAPSHOT dependency cannot be built because of missing (evicted) parent 0.0.1-SNAPSHOT. The point is that failing to build lib 0.0.1-SNAPSHOT pom file should not result in a app failed build, as there exists another valid lib 0.0.2-SNAPSHOT (having

Re: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

I'm surprised the transitive dependency to that parent succeeds, unless it's ranged. For the others, in order to determine the dependency tree, and thus any transitive dependencies, and so on, the entire pom needs to be present. A parent is part of that. If the parent is of a fixed version (all

project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

Hi All, The title says it all. Any suggestions how to overcome this issue ? Explanation below. Let the projects be: ‘parent’ : the parent pom of the ‘lib’ library just below ‘lib’ : the library ‘app’ : the application dependent on ‘lib’ through a version range. (all three