I can tell you we have the following directory available
/www/cvs.apache.org/repository/
with a few builds within it that the incubator folks are using. It is
accessable over http (maven) using
http://cvs.apache.org/repository/
-Mark
Joe Germuska wrote:
Back in January when Mark Diggory was
Back in January when Mark Diggory was establishing the IBiblio rsync
process, he also mentioned an Apache nightly-build repository.
http://article.gmane.org/gmane.comp.jakarta.commons.devel/39469
It looks like that hasn't been set up. Was it ruled out? Or has it
just not happened yet?
We're
Ryan Hoegg wrote:
In any case, in my mind one should not be deploying SNAPSHOTs to the
"release" repository anyway, its only for releases. Further, it seems
to me to be a dubious practice to cut a release with a SNAPSHOT
dependency in project.xml.
--
Ryan Hoegg
ISIS Networks
http://www.isisn
Mark R. Diggory wrote:
__matthewHawthorne wrote:
Paul Libbrecht wrote:
Well... no, that means you would depend on daily build for all of
Apache projects which definitely not the intent.
Is it really a problem to have >one< project-name-SNAPSHOT.jar ?
(and no dated things)?
I disagree. I
__matthewHawthorne wrote:
Paul Libbrecht wrote:
On 30-Jan-04, at 06:20 Uhr, __matthewHawthorne wrote:
Mark R. Diggory wrote:
A.) Version Releases
/www/www.apache.org/dist/java-repository
b.) Daily Builds
/www/cvs.apache.org/builds/java-repository
c.) Archives
/www/archives.apache.org/dist
Yes, order of these would be up to the developers. But, ordering of
these does not necessarily dictate with file is used in the case of
snapshot, I believe in such a case the snapshots are compared in the two
repositories for underlying version backing them, the newest of the two
versions is us
At 10:38 PM -0500 1/29/04, Mark R. Diggory wrote:
Because only /www/www.apache.org/dist/java-repository is mirrored to
ibiblio, only versioned releases get exposed through the default
maven repository settings. Apache developers who wish to be testing
against the "bleeding edge" only need to add
Paul Libbrecht wrote:
On 30-Jan-04, at 06:20 Uhr, __matthewHawthorne wrote:
Mark R. Diggory wrote:
A.) Version Releases
/www/www.apache.org/dist/java-repository
b.) Daily Builds
/www/cvs.apache.org/builds/java-repository
c.) Archives
/www/archives.apache.org/dist
I think I like this idea. The
On 30-Jan-04, at 06:20 Uhr, __matthewHawthorne wrote:
Mark R. Diggory wrote:
A.) Version Releases
/www/www.apache.org/dist/java-repository
b.) Daily Builds
/www/cvs.apache.org/builds/java-repository
c.) Archives
/www/archives.apache.org/dist
I think I like this idea. The abundance of snapshot
Thanks,
We'd have to do some consulting with the Ibiblio folks, they have a
policy of not allowing rsyncing with deletions, they prefer to maintain
archival copies of everything.
We also need to consider how we will approach snapshots vs version
releases. The current strategy I'm proposing is
Mark R. Diggory wrote:
rsync is now active between apache and www.ibiblio.org/maven every 4 hours.
minotaur.apache.org:/www/www.apache.org/dist/java-repository
contents are now rsynced directly to
www.ibibilio/maven.
by ibibilio.
This means anything you place into java-repository will be avail
Release Managers,
rsync is now active between apache and www.ibiblio.org/maven every 4 hours.
minotaur.apache.org:/www/www.apache.org/dist/java-repository
contents are now rsynced directly to
www.ibibilio/maven.
by ibibilio.
This means anything you place into java-repository will be available
12 matches
Mail list logo
