On 2014-07-07, 1:56, Mark Derricutt wrote:
That would in part align things with Aether's somewhat annoying/retarded
behaviour of saying "oh I see com.acme:special tool:1.0-alpha-1" but it
came from repo-1, not repo-2 - so "suck it up - I can't resolve this.".
I can understand the idea behind this - two artefacts from two different
repositories _may_ share the same GAV and yet be totally different, but
I find that to be so rare that that I probably never want this to not
resolve ( that causes lots of annoying issues with using a mirror, and
having to temporarily disable said mirror ).
I don't think this has much/anything to do with the same GAV coming from
different remote URLs. The project does not have access to repo-1 and
Maven does not know if repo-2 has the artifact. Without this check
project may get access to artifacts that simply happen to be cached
locally during some prior build, which I rather strongly believe is a
bad thing.
--
Regards,
Igor
I could see this change also breaking under mirrors, or maybe that's
just when using mirror:*
On 5 Jul 2014, at 4:56, Robert Scholte wrote:
To me it would make sense if you could add a reference to the
repository per dependency, like
<dependency>
<groupId>com.acme</groupId>
<artifactId>specialtool</artifactId>
<version>1.0-alpha-1</version>
<repositoryId>acme-store</repositoryId> <!-- only look in this repo, I
know it's not in Central -->
</dependency>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
