Thx, Yoav!
In that case there is a bug in 2.1 (may affect other versions too):
The case:
1. NOone accessed com.test:foo at all in the past (from NEWR)
2. there is NO com.test:foo in NEWR
3. there are com.test:foo versions with metadata in OLDR
4. release of com.test:foo happens (to NEWR)
5. accessing http://NEWR/repo/com/test/foo/maven-metadata.xml returns
ONLY the NEW foo version
Fix by hand:
1. Access http://NEWR/oldr/com/test/foo/maven-metadata.xml -- assuming
ID of Remote Repo to OLDR is oldr
2. Now accessing http://NEWR/repo/com/test/foo/maven-metadata.xml returns
ALL version
It looks like if there is no information about other metadata new release
shades all other metadata.
It would be nice if there would be a way to force "recalculation" of
metadata.
Regards,
Lóránd Somogyi
http://lorands.com
http://photols.com
On Tue, Oct 20, 2009 at 3:44 PM, Yoav Landman <[email protected]> wrote:
> 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 <[email protected]
> > 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
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
