Dain Sundstrom wrote:
On Jan 5, 2005, at 10:26 AM, Mark R. Diggory wrote:
Thanks for your response Dain,
Dain Sundstrom wrote:
On Jan 4, 2005, at 8:34 PM, Mark R. Diggory wrote:
Please excuse the cross post. I'm planning to run some commands on the java-repository to remove interim builds and SNAPSHOTS. Specifically, I'll be running:
If you remove SNAPSHOTS, it not only can it break head branches of projects,
Can you explain this further, I'm not sure what your suggesting here. Are you referring to content outside of /www/www.apache.org/dist/java-repository? Its important to point out that I'm only suggesting modification of content in the repository, not modification of any other content inside dist/...
it can break milestone "source" releases that people are still
using. -dain
Well, the http://www.ibiblio.org/maven repository will still maintain all the SNAPSHOTS/interim builds I am planning on removing. That rsync does not delete files. So users of Maven working solely with the www.ibiblio.org/maven repository will not experience any of these changes.
If it is really the case that Maven users are going to dist/java-repository instead www.ibiblio.org/maven we should alert them, dist/java-repository is in practice just for publishing Apache jars to ibiblio (though we have visions of its usage for other goals in the near future).
For Apache developers using Maven, what I recommend is to continue using www.ibiblio.org to resolve dependencies for milestone and release builds. Then, to actually do any interim, snapshot or dated builds into
http://cvs.apache.org/repository
which is not mirrored.
I can say that I was not aware of the policy, so I would assume other are not. If there are any projects that were using that location as a maven repo, their builds will break. Also if someone shipped a source distribution that needs one of these files, it will break, which means there would be no way to reproduce a historical build from a source distribution.
-dain
Yes, I'm not sure that we can refer to it accepably as "a policy", as much as a "best practice".
Well, if we take the latest release of Commons Math for instance. From both a Maven and Ant standpoint the distributions dependecies are resolved to/against ibibilio:
<get dest="${libdir}/commons-logging-1.0.3.jar" usetimestamp="true" ignoreerrors="true" src="http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.3.jar";>
</get>
<get dest="${libdir}/commons-discovery-0.2.jar" usetimestamp="true" ignoreerrors="true" src="http://www.ibiblio.org/maven/commons-discovery/jars/commons-discovery-0.2.jar";>
</get>
In Maven, the repository used to get downloads from is not a project attiribute, it is a user decision/configuaration of the client. So really, a project that ends up with any dependency downloads directly from dist/java-repository is not the best solution, ibiblio is the more persistent and canonical point to be downloading from at this point.
It might be good to go through the Apache projects that are in java-repository and see if any are packaged to download dependencies from there, I doubt it that here would be any occurances however. As a majority of the files were originally published to/against ibiblio in the first place.
cheers, MArk
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
