Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of archie.cobbs@gmail.com
 designates 209.85.198.248 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=a/tvv2wDujAnqKYQYiaZ8BGTgmXyQW2r+/07g0Lun4SUHbQcMYeDFy7IAkxZdnDNETRthf8BWCANWHpkpHmNhnj91JpXbRXhKtUYOeX8P5HRKkVg0IYd31c53xn3A2Jb17SCEarBcStKAmd0CMGPrco5xny3jQ9q+GAh1LlDPJw=
Message-ID: <3bc8237c0804171159p2ac61cffu1ac9336f8ee7d1f8@mail.gmail.com>
Date: Thu, 17 Apr 2008 13:59:19 -0500
From: "Archie Cobbs" <archie@dellroad.org>
Sender: archie.cobbs@gmail.com
To: ivy-user@ant.apache.org
Subject: Re: Ivy RoundUp Repository - feedback requested
In-Reply-To: <635a05060804171110y624c7bb6xb578561687c17549@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_878_12888545.1208458759917"
References: <3bc8237c0804150806j41812cdfv9938be9f1da0adce@mail.gmail.com>
	 <e9d8a2610804170240ra8d435w4e4f15c97f4257a0@mail.gmail.com>
	 <3bc8237c0804170731p16999923g5048b0bc15bb017f@mail.gmail.com>
	 <EE7473F9E5EC3D4CBC1CDDD38BC1FA3206DFB4C3@CWA0020EX.ccsouth.cccore.com>
	 <635a05060804171110y624c7bb6xb578561687c17549@mail.gmail.com>

------=_Part_878_12888545.1208458759917
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Thu, Apr 17, 2008 at 1:10 PM, Xavier Hanin <xavier.hanin@gmail.com>
wrote:

> It depends how you consider the roundup repository. I think its intent is
> to
> be a kind of meta repository: it contains metadata helping to build an
> actual repository. Maybe what's confusing is that archie suggest to use it
> as a repository directly. IMO this is required only until we can get
> enough
> support to have a good hosting for the actual repository. Then both the
> meta
> repository and the actual repository would make sense: the meta repository
> is helpful for people who want to create their own repository, and easier
> to
> update than a repository made by hand. But it isn't used directly from
> Ivy.
> The actual repository is the only thing that is used by mere users.
>

There are actually three possibilities...

   1. Builder Repository: repository contains ivy.xml and builder.xml
   files only, and the user is required to use the builder resolver, whereby
   the actual artifacts are downloaded and extracted as necessary at resolution
   time.
   2. Builder Repository + Artifact repository: same as above, but you
   configure your resolver with the "resourceURL" attribute (which overrides
   the normal resource URLs), which points to the Artifact repository
   containing all of the ZIP/TGZ files that you need to download. The Artifact
   repository could be local or community/online. This means we don't have to
   rely on each/every project's server being reliable.
   3. Build-your-own-Repository: we would add a new ant task in the Ivy
   RoundUp build.xml that actually executes all the builder.xml
   download/extract instructions for every module in the repository to get all
   the artifacts and then combines those artifacts with the ivy.xml files to
   create a normal Ivy repository.

Correlating with Xavier's comments: #3 == "meta repository" whereas #1 =
"repository directly".

The important concept here is *separation of the meta-data from the data*.

Also important is *not forcing the requirement for a high capacity, high
bandwidth public server*.... I'll repeat my claim that this is important
based on the evidence that nobody has yet volunteered to replace Ivyrep.

If someone is willing to host a normal repository, then options #2 or #3
make sense. If not, then #1 makes sense.  But it is flexible enough to work
in any/all of these ways. I think we should start with #1 and then we can
move to #2 or #3 if and when someone volunteers the additional servers and
disk space.

-Archie

-- 
Archie L. Cobbs

------=_Part_878_12888545.1208458759917--