I was looking for just one physical location to manually put release
packages, with any mirroring/grouping/multiple locations to be done
automagicly. Not wanting to break anything or remove old links, just
wanting efficient use of computer resources and simple processes to follow.
Jeff.
Stefa
On Sun, 16 Feb 2003, Craig R. McClanahan <[EMAIL PROTECTED]> wrote:
>> > -1 on removing the nightly builds directory
>> > (jakarta.apache.org/builds/jakarta-commons/nightly/).
>>
>> But shouldn't that be on cvs.apache.org? Again, rewrite rules are
>> your friend for people using the old URLs.
>>
On Sun, 17 Feb 2003, Stefan Bodewig wrote:
> Date: 17 Feb 2003 08:34:37 +0100
> From: Stefan Bodewig <[EMAIL PROTECTED]>
> Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: help - multiple location of commons relea
On Sat, 15 Feb 2003, Craig R. McClanahan <[EMAIL PROTECTED]> wrote:
> On Sat, 15 Feb 2003, Jeffrey Dever wrote:
>> 2) jakarta.apache.org/builds/jakarta-commons should be deprecated,
>> removed or replaced with a softlink or a forward.
>
> -1 on removing the nightly builds directory
> (jakarta.apa
On Thu, 13 Feb 2003, Jeffrey Dever <[EMAIL PROTECTED]> wrote:
> Hmmm, so even though www.apache.org and jakarta.apache.org are
> served from the same physical machines, we are to keep two binary
> and source repositories up to date with new releases? Why isn't one
> just a softlink of the other?
On Thu, 13 Feb 2003, Jeffrey Dever wrote:
> There appears to be (at least two) locations for releases that need to
> be manually updated: one on jakarta.apache.org and one on
> www.apache.org. Are we supposted to keep both of these manually
> updated? Why are there two? I have an account on d
On Sat, 15 Feb 2003, Jeffrey Dever wrote:
> Date: Sat, 15 Feb 2003 12:24:34 -0500
> From: Jeffrey Dever <[EMAIL PROTECTED]>
> Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]>
> To: Jakarta Commons Developers List <[EMAIL PROTECTED]>
> Subject
Here are my suggestions for commons regarding release processes:
1) All release packages should be copied to
www.apache.org/dist/jakarta/commons to allow for mirroring.
2) jakarta.apache.org/builds/jakarta-commons should be deprecated,
removed or replaced with a softlink or a forward
3) single i
On Friday, February 14, 2003, at 03:27 AM, Henri Yandell wrote:
On Thu, 13 Feb 2003, Jeffrey Dever wrote:
Hmmm, so even though www.apache.org and jakarta.apache.org are served
from the same physical machines, we are to keep two binary and source
repositories up to date with new releases? Why is
>A version of Apple's tar had some kind of bug. I'm not sure if that's
>still there. The main problem with OS X is that the default [and only
>reasonable] filing system is case insensitive [windows has this problem
>though], and more painfully, the default unzipper stuffit likes to chop
>filenames
On Thu, 13 Feb 2003, Mark R. Diggory wrote:
>
>
> Henri Yandell wrote:
> > Is there any need to support both tar.gz and .zip? With the exception of
> > some minor pain on Apple machines for tar.gz [although I've never had this
> > myself], it seems we could ditch one of these distribution mechan
Henri Yandell wrote:
On Thu, 13 Feb 2003, Jeffrey Dever wrote:
And speaking of releases, why in commons do we have two packages for
each release, one for source and one for binaries? These are small
components where the biggest thing about them is the generated javadoc
which is in both. I f
On Thu, 13 Feb 2003, Jeffrey Dever wrote:
> Hmmm, so even though www.apache.org and jakarta.apache.org are served
> from the same physical machines, we are to keep two binary and source
> repositories up to date with new releases? Why isn't one just a softlink
> of the other?
+1. I've not done a
Hmmm, so even though www.apache.org and jakarta.apache.org are served
from the same physical machines, we are to keep two binary and source
repositories up to date with new releases? Why isn't one just a softlink
of the other?
And speaking of releases, why in commons do we have two packages for
Thanks for clearing that up :-)
robert burrell donkin wrote:
just to clear this up, jelly isn't using ibiblio to distribute an
official apache release. jelly is available from ibiblio but the
official distribution of apache software will always be done from the
apache web site.
- robert
On
hi jeff
the www.apache.org location is mirrored. see
http://www.apache.org/dev/mirrors.html.
the policy i've used for the latest beanutils and digester releases is to
force users to download from the mirrored site. if you do want to keep a
release available from the old location, there isn't r
just to clear this up, jelly isn't using ibiblio to distribute an official
apache release. jelly is available from ibiblio but the official
distribution of apache software will always be done from the apache web
site.
- robert
On Thursday, February 13, 2003, at 08:30 PM, Mark R. Diggory wrote:
Just to put it out there, I also notice a number of commons subprojects
(jelly for one) are using http://www.ibiblio.org/maven/ for
distribution. Maybe its not a stretch to dream of the day that a
"www.javafind.net/www.jarfind.net" (i.e. www.rpmfind.net) service exists ;-)
-Mark Diggory
Jeffr
There appears to be (at least two) locations for releases that need to
be manually updated: one on jakarta.apache.org and one on
www.apache.org. Are we supposted to keep both of these manually
updated? Why are there two? I have an account on deadalus, but where
would I even go to modify what
19 matches
Mail list logo
