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

Re: [DISCUSSION] finishing Aether import: help find a new name

true: I know it sounded familiar... :) this artifact seems used by maven-remote-resources-plugin only And if you look at the content, it contains a little helper to resolve dependencies: we should probably deprecate it at the end If there is no objection, I'll update code in a few days to

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 2016-08-03 um 22:04 schrieb Jason van Zyl: Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver for the package names is more consistent with the other naming in that document. Maves sense, probably this project should be named maven.a.o/artifact-resolver

Re: [DISCUSSION] finishing Aether import: help find a new name

Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver for the package names is more consistent with the other naming in that document. > On Aug 3, 2016, at 12:30 PM, herve.bout...@free.fr wrote: > > true: I know it sounded familiar... :) > > this artifact seems used by

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

Re: [DISCUSSION] finishing Aether import: help find a new name

It's really all about JARs... "Java Artifact Repository Specification" JARS Happenstance. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [DISCUSSION] finishing Aether import: help find a new name

It's just a name - I know. Personally, I disagree with 'resolver'. It's so much more. It also abstracts the transfers/transports etc. It is an abstraction to manage and access a repository (whatever that may mean) of artifacts (whatever that may mean) by employing a special directory structure and

Re: [DISCUSSION] finishing Aether import: help find a new name

I proposed Maven Artifact Universe, but received no response. Am 2016-08-03 um 23:32 schrieb Christian Schulte: It's just a name - I know. Personally, I disagree with 'resolver'. It's so much more. It also abstracts the transfers/transports etc. It is an abstraction to manage and access a

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 08/03/16 um 23:47 schrieb Michael Osipov: > I proposed Maven Artifact Universe, but received no response. Pretty close. In the Java universe we got used to talk about JSRs and JEPs and things like that. I am all for something along "Maven Artifact Repository Specification" and corresponding

Re: [DISCUSSION] finishing Aether import: help find a new name

Guys. Just because it fits perfectly the Java universe. "Java Artifact Repository Specification". JARS Regards, -- Christian Am 04.08.2016 um 00:21 schrieb Christian Schulte: Am 08/03/16 um 23:47 schrieb Michael Osipov: I proposed Maven Artifact Universe, but received no response. Pretty

Re: [DISCUSSION] finishing Aether import: help find a new name

I much prefer MARS, especially if you can come up with corresponding wordplay for VENUS… ;-) Seriously, the overlap with Java ARchive is bound to be confusing, and might even make people think that the component has something to do with them. Ralph > On Aug 3, 2016, at 4:29 PM, Christian