Noel J. Bergman [EMAIL PROTECTED] wrote on 01/03/2003 06:45:42 AM:
[snip]
How much should be encoded in a URI, and how much in data associated
with
the URI? You seem to be trying to encode all of the data into the URI
naming space. Why not have a single URI for the target, and then
trigger
Leo Simons wrote:
Hi all,
(sorry for the massive crosspost up front, as this is a proposal that
should in the end come from the various PMCs towards the infrastructure
team I'm doing lots of CCing, just once)
FYI, the JPackage project where I'm also involved, as set up
a Java RPM centric
Henri Gomez wrote:
FYI, the JPackage project where I'm also involved, as set up
a Java RPM centric distribution where you could find many
(still not all) apache's java projects.
http://.jpackage.org/
Hi, Henry. I'm using them and they are awful to simplify maintenance of
linux rpm based
On Fri, 28 Feb 2003, Nicola Ken Barozzi wrote:
Seeing the interest it has raised, I tend to think think it's time to
get the act together and start working on it. I'd like to propose this
for incubation ASAP, so to not loose momentum.
...
Codebases or part of codebases that could convole
Costin Manolache wrote:
On Fri, 28 Feb 2003, Nicola Ken Barozzi wrote:
Seeing the interest it has raised, I tend to think think it's time to
get the act together and start working on it. I'd like to propose this
for incubation ASAP, so to not loose momentum.
...
Codebases or part of
Nick,
As long as you want to start with first principles ...
If we have a layout and metadata we agree on - any tool could work.
If it is an ant task or a perl program or we just rsync - it doesn't
matter.
A somewhat standard layout is the important part.
--On Wednesday, February 26, 2003 6:15 PM +0100 Leo Simons
[EMAIL PROTECTED] wrote:
my take: keep everything. Again, policy should be the same as for
the contents of /dist/. I dunno if there is an asf-wide policy for
that...looking at http://www.apache.org/dist/httpd/old/, those guys
don't share
Costin Manolache [EMAIL PROTECTED] writes:
Few simple questions:
Should we use 2 different dirs for src and binary distribution ? Or
maybe 3 dirs ( src, bin, doc ) ?
Why duplicate the existing distributions? They're available, mirrored and
well understood.
Are milestone builds
On Fri, 28 Feb 2003 [EMAIL PROTECTED] wrote:
In other words - as long as maven decisions affect only maven - I don't
care. But if it affects other projects, and the repository certainly does
- then the PMCs of those projects or the apache community are the ones
that decide.
On Thu, 27 Feb 2003 [EMAIL PROTECTED] wrote:
Few simple questions:
Should we use 2 different dirs for src and binary distribution ? Or
maybe 3 dirs ( src, bin, doc ) ?
Why duplicate the existing distributions? They're available, mirrored and
well understood.
+1
I was just
On Wed, 26 Feb 2003, Noel J. Bergman wrote:
- the ASF repository shall contain ASF jars, which don't
require oversight beyond the issuing PMC.
- the ASF repository should contain shared third party
jars for which the ASF has approved their use and
distribution.
- the ASF
--- Costin Manolache [EMAIL PROTECTED] wrote:
On Fri, 28 Feb 2003 [EMAIL PROTECTED] wrote:
In other words - as long as maven decisions
affect only maven - I don't
care. But if it affects other projects, and the
repository certainly does
- then the PMCs of those projects or
Not sure what you mean by lead ( do you propose a new PMC with Dion as
chair ? ). I'm +1 on Dion - however the layout and recommendations must be
decided by the normal apache community process
I meant as in chair, except that it wouldn't be a PMC, so I don't know if
the word chair would apply.
Noel J. Bergman wrote:
Not sure what you mean by lead ( do you propose a new PMC with Dion as
chair ? ). I'm +1 on Dion - however the layout and recommendations must be
decided by the normal apache community process
I meant as in chair, except that it wouldn't be a PMC, so I don't know if
the
Noel Bergman writes:
I like the idea of a central repository. It would simplify the issue by
centralizing maintenance of jars and licenses. I just want to know how
it
is going to operate. A joint operation between Ant and Maven?
Infrastructure?
[I won't even get into the question of why
Conor,
I could be wrong, but I don't believe that Dion was refering to the
repository; rather he was commenting in response to my aside regarding Ant
and Maven:
On Wed, Feb 26, 2003 at 09:48:42PM +1100, [EMAIL PROTECTED] wrote:
Noel Bergman writes:
I like the idea of a central repository. It
Costin Manolache wrote:
On Tue, 25 Feb 2003, Leo Simons wrote:
files in /dist/java-repository besides perhaps HEADER.html and
README.htmls...
Few simple questions:
Should we use 2 different dirs for src and binary distribution ? Or maybe
3 dirs ( src, bin, doc ) ?
based on current
Costin Manolache wrote:
What policy should we use for removing older versions ( or we just keep
everything ) ?
my take: keep everything. Again, policy should be the same as for the
contents of /dist/. I dunno
if there is an asf-wide policy for that...looking at
Leo Simons wrote:
do that, but the big disadvantage with deviating from the existing
maven/centipede/ruper
practice is that it deviates from that practice, thus requiring work
and reducing compatibility. If you
feel like holding a vote, by all means feel free, I'll probably vote
-1 for
My proposal is that Dion Gillard be asked to chair a repository committee.
He is the most familar with the issues, he works with a lot of the Java
technologies (Tomcat, Ant, Maven, James, Jetspeed, Struts, Turbine), and
although he is a Maven fan, he is agnostic in terms of ensuring that all
build
Leo,
As you have seen from some of our exchange and Costin's comments, there are
differing views on how to make use of the repository. Costin and I seem to
be of the option that a significant portion of the value of the repository
comes from sharing and centralizing the managment of
On Wed, 26 Feb 2003, Nick Chalko wrote:
So I am for
/projectname/[subproject]/[version]/file[-version].jar
That leo suggested.
I'm not sure that's what Leo suggested.
Having the version in both dir and jar seems a bit too much. The common
practice in many projects ( at least in jakarta )
Costin Manolache wrote:
On Wed, 26 Feb 2003, Nick Chalko wrote:
So I am for
/projectname/[subproject]/[version]/file[-version].jar
That leo suggested.
I'm not sure that's what Leo suggested.
The [] imply optional. But my main point is Centipede will adapt to
whatever Apache uses.
Costin,
I agree with pretty much all of your particulars. To summarize, if I might:
- the ASF repository shall contain ASF jars, which don't
require oversight beyond the issuing PMC.
- the ASF repository should contain shared third party
jars for which the ASF has approved their use
Noel J. Bergman wrote:
As you have seen from some of our exchange and Costin's comments, there are
differing views on how to make use of the repository. Costin and I seem to
be of the option that a significant portion of the value of the repository
comes from sharing and centralizing the
Leo Simons wrote:
you get an ok on that from the board and/or the infrastructure team,
and consensus across the
community, and I'll be absolutely 100% behind any such plan.
scratch that, I'm in a Just Do It mood today. Just sent a message to
the board (who are
reading already anyway, but hey,
you get an ok on [sharing and centralizing the managment
of ASF-acceptable third party jars] from the board and/or
the infrastructure team, and consensus across the community,
and I'll be absolutely 100% behind any such plan.
I can't see how it would be acceptable to anyone without all of
My opinion is that the board should take this suggestion very seriously.
Original Message
Subject: RE: [proposal] daedalus jar repository (was: primary
distribution location)
Date: Wed, 26 Feb 2003 14:54:20 -0500
From: Noel J. Bergman [EMAIL PROTECTED]
Reply-To: community
Sam Ruby wrote:
- Leo (avalon pmc member acting sort-of on behalf of the java peeps
using the
lazy consensus model and the Just-Do-It-in-the-event-of-consensus
mindset :D)
I like that mindset. Note: the essence of lazy consensus is that such
actions are immeditely rolled back if an issue is
On Mon, 24 Feb 2003, Noel J. Bergman wrote:
I thought this was for Apache only jars. Just a place for projects to
place there Released jars as a compliment to the zip and qz
distributions. So there should be no license issues.
Well, I'm still waiting to hear about some of this. From
Noel J. Bergman wrote:
Which PMC is going to oversee the repository?
all PMCs whose committers 'commit' to the repository should maintain
some oversight. I
don't think there's an official precedent wrt how this works @ apache.
It might be possible
to get the infrastructure peeps to take on the
all PMCs whose committers 'commit' to the repository should maintain
some oversight.
Infrastructure hasn't considered that a good model for the Wiki, and I don't
know that it would work any better for the repository. Someone needs to
take responsibility for the oversight.
I'm not suggesting
Noel J. Bergman wrote:
all PMCs whose committers 'commit' to the repository should maintain
some oversight.
Infrastructure hasn't considered that a good model for the Wiki, and I don't
know that it would work any better for the repository. Someone needs to
take responsibility for the
On Tue, 25 Feb 2003, Leo Simons wrote:
files in /dist/java-repository besides perhaps HEADER.html and
README.htmls...
Few simple questions:
Should we use 2 different dirs for src and binary distribution ? Or maybe
3 dirs ( src, bin, doc ) ?
Are milestone builds acceptable ? Should we get
On Tue, 25 Feb 2003, Noel J. Bergman wrote:
all PMCs whose committers 'commit' to the repository should maintain
some oversight.
Infrastructure hasn't considered that a good model for the Wiki, and I don't
know that it would work any better for the repository. Someone needs to
take
Brian Behlendorf wrote:
+1. I see nothing wrong with the plan. Hopefully Ant can be made smart
enough to pull the jars down from mirrors, too.
Patches always welcome, Brian :-)
Conor
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On Fri, 21 Feb 2003, Conor MacNeill wrote:
Brian Behlendorf wrote:
+1. I see nothing wrong with the plan. Hopefully Ant can be made smart
enough to pull the jars down from mirrors, too.
Patches always welcome, Brian :-)
The mirror CGI script should be able to handle this fairly
37 matches
Mail list logo
