Re: [Artifactory-users] maven-metadata.xml aggregation behavior

[Yoav L. <yo...@jf...>]

Merged maven-metadata.xml containing all versions reachable from the virtual
repository 'http://NEWR/repo' - from both NEWR and OLDR (assuming the user
making the request has enough permissions to populate artifacts in the OLDR
cache).

On Tue, Oct 20, 2009 at 10:07 AM, Lóránd Somogyi
<lor...@gm...>wrote:

> HI!
>
> I'm a bit confused, so please help me understand the intention...
>
> A little bit of background:
>
>    - we have one simple repository (a'la repo1.maven.org) for older
>    releases -- let's call this one OLDR
>       - in simple folder/file structure
>       - with generated maven-metadata.xml
>       - serviced by Apache HTTPD
>       - we have an Artifactory instance used by all users -- lets call
>    this NEWR
>    - we have a Remote Repository defined which points to OLDR
>
> Now. If I have in OLDR: com.test:foo versions 1.1, 1.2, 1.3. 2.0 (with
> correct maven-metadata.xml). In NEWR, I have: com.test:foo versions 2.1,
> 3.0, 3.1. - all produced with maven release plugin.
>
> What if I ask for: *http://NEWR/repo/com/test/foo/maven-metadata.xml* what
> should I get?
>
> Thanks,
>
> Lóránd Somogyi
> http://lorands.com
> http://photols.com
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Artifactory-users mailing list
> Art...@li...
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>