Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: pass (hermes.apache.org: domain of steve.loughran@gmail.com
 designates 64.233.184.203 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=WZgkybbYm/X1NB0Y1Wm3vdsKL1y7Ohmoash5xhpbDmTVcqS//oiX3QdBP1d1SBUFWlAys45Lc/4eAMy1IYXA4kvrtYhvUFhwkK9EdQS1qGO+sfwHVY12D+YL04zCQZwHiRfmdIOv3J5rPaceNKERjnpV6idJKiSQTMszWEbULFo=
Message-ID: <c84a50780505040434561ff8d@mail.gmail.com>
Date: Wed, 4 May 2005 12:34:06 +0100
From: Steve Loughran <steve.loughran@gmail.com>
Reply-To: Steve Loughran <steve.loughran@gmail.com>
To: repository@apache.org
Subject: Re: Proposal for a centralized Eclipse update manager site for Apache
 projects/software
In-Reply-To: 
 <OFD1161EA3.5BE6AC9F-ON85256FF6.0079998D-85256FF6.0079EC56@ca.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <c84a507805050313545361b55c@mail.gmail.com>
	 <OFD1161EA3.5BE6AC9F-ON85256FF6.0079998D-85256FF6.0079EC56@ca.ibm.com>

On 5/3/05, Jeffrey Liu <jeffliu@ca.ibm.com> wrote:
> =20
> Hi Steve,=20
> =20
> Configure in this case means the user goes to the Eclipse perference page=
,
> choose the version of Tomcat that was downloaded, and point Eclipse to th=
e
> location where it was unzipped. Nothing major, but not obvious to novice
> users. Although I'm not similar with what autonomic-system-management is,=
 I
> don't think this is anything near that.=20

Well, that's all right then. I was worried you were thinking of
configuring tomcat to find a spare port, open a hole in the firewall,
etc etc.

But if you arent doing that, then this proposal is purely for the
Eclipse IDE itself?

That's a bit, well, limited.=20

We currently have three ways of distributing stuff
 -on the web, for download
 -as rpms, including jpackage rpms of java stuff
 -as maven/maven2 downloads

RPMs are interesting because although linux-centric (and redhat
centric, to be precise), there are a lot of tools out there than can
pump them out to systems in a cluster; you get good management.

maven repositories are fun because every JAR is on a URL; you can pass
them to a URL classloader as is if you want. The .pom also declares
dependencies for transitive work; a bit like debian apt-get.

We are just starting to roll out Maven2 support, both in Apache and
outside it. I am not (yet) convinced we need
yet-another-archive-format with another set of distributables, and if
it only benefited one IDE, I dont think it is justifiable. It would
surely be better if we had

-a gui client that could work with the existing Apache repositories
-a client build on AWT for broadest cross platform execution.=20
-some way of pushing out packages to multiple systems in a cluster
-support per/user, per-system packages
-good auditing to determine package set (with JMX integration)

That is, a Java successor to all the rpm management tools.

Incidentally, one pressing problem with the maven repositories is
there is no easy way to fetch Sun stuff. That is, if I want to use
Axis with mail.jar and activation,jar, you cant get those from the
Apache site for legal reasons. Do you propose any solution to the
clickthrough licensing problem?

-steve