Propagating repository to a new release

[BrentAtSerena <bj...@serena.com>]

I have an Archiva server that I have inherited. I don't have a lot of
experience with Archiva and I'm hoping to adapt it to my own uses as it
doesn't currently do a good job of supporting everything I need it to do.

Currently, when a component is being built and it uses a jar it uploads the
jar into the archiva server. When another component is built that uses the
previous component it retrieves the jar from archiva (pretty standard I
think).

Basically, I need an easy way(not me uploading each jar manually) to
populate a new release with all the artifacts from the previous release.

There may be actually good ways to do this.

Some bad ways I've researched and I think won't work are:
1. Faking it with virtual repositories linked to the old release repository
(I think the read-only nature of this prevents this from working for me as
it will fail when I try to upload).
2. Setting the previous release as a source the new release can check. (This
would probably work but I worry about propagating old jars across multiple
releases).

If someone has a good solution for this it would be much appreciated.
-- 
View this message in context: http://old.nabble.com/Propagating-repository-to-a-new-release-tp28710861p28710861.html
Sent from the archiva-dev mailing list archive at Nabble.com.

Re: Propagating repository to a new release

[Brett Porter <br...@apache.org>]

I'm not sure I understand what you mean by a "release" why would you want to populate a new one with the JARs of an old one?

Archiva is typically used for Maven builds, which composes a release of one particular distribution from various other releases of other libraries, without duplicating anything across releases.

- Brett

On 28/05/2010, at 12:13 PM, BrentAtSerena wrote:

> 
> I have an Archiva server that I have inherited. I don't have a lot of
> experience with Archiva and I'm hoping to adapt it to my own uses as it
> doesn't currently do a good job of supporting everything I need it to do.
> 
> Currently, when a component is being built and it uses a jar it uploads the
> jar into the archiva server. When another component is built that uses the
> previous component it retrieves the jar from archiva (pretty standard I
> think).
> 
> Basically, I need an easy way(not me uploading each jar manually) to
> populate a new release with all the artifacts from the previous release.
> 
> There may be actually good ways to do this.
> 
> Some bad ways I've researched and I think won't work are:
> 1. Faking it with virtual repositories linked to the old release repository
> (I think the read-only nature of this prevents this from working for me as
> it will fail when I try to upload).
> 2. Setting the previous release as a source the new release can check. (This
> would probably work but I worry about propagating old jars across multiple
> releases).
> 
> If someone has a good solution for this it would be much appreciated.
> -- 
> View this message in context: http://old.nabble.com/Propagating-repository-to-a-new-release-tp28710861p28710861.html
> Sent from the archiva-dev mailing list archive at Nabble.com.
> 

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/