Txs Benjamin!
I don't think it is that different, because my real problem is that I cannot distinguish between those artifacts because of that.
So the problem of _retrieving_ those artifacts (and detecting problems within them) maybe can be solved by storing them in a different way?
In other words, the original problem:
> project ---depends-on---> A ---depends-on---> B
could be solved IF we can distinguish between the repository scope of the artifacts as raised in [1].
e.g. even if A introduces a fully blown repo2 (containing B),'project' itself could still use the artifacts from central. Kind of a repo-resolve hierarchy analogue to a classloader hierarchy. Resolving version crashes and things might get tricky though, but should be doable.
LieGrue,
strub
[1]
http://jira.codehaus.org/browse/MNG-3056----- Ursprüngliche Mail ----
> Von: Benjamin Bentmann <
benjamin.bentmann@...>
> An: Maven Developers List <
dev@...>
> Gesendet: Freitag, den 30. Oktober 2009, 12:01:28 Uhr
> Betreff: Re: AW: [DISCUSS] Handling of repositories in POMs of dependencies
>
> Mark Struberg wrote:
>
> > But in my local repo, all the artifacts from those repositories gets merged to
> a single big landfill.
>
> That seems to be a completely independent issue, isn't it? The question I
> originally raised was about what repositories ought to be considered during
> dependency resolution, not where we should store the local artifacts/metadata
> retrieved from them.
>
> So please consider to move this part of the discussion off into another thread,
> keeping this thread focused on its actual topic and thereby easing review of the
> thread.
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
dev-unsubscribe@...
> For additional commands, e-mail:
dev-help@...
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
