I've been reviewing the contents of avalon jars directories and of java-repository/(avalon|cornerstone|excalibur).../jars/ and have come to the following conclusion, in many (if not all) cases the jars in java-repository are the same and newer versions than in dist/avalon.
Here's a sampling of comparisions:
http://www.apache.org/dist/avalon/avalon-activation/jars/ http://www.apache.org/dist/java-repository/avalon-activation/jars/
http://www.apache.org/dist/avalon/avalon-composition/jars/ http://www.apache.org/dist/java-repository/avalon-composition/jars/
http://www.apache.org/dist/avalon/cornerstone-connection-api/jars/ http://www.apache.org/dist/java-repository/cornerstone-connection/jars/
http://www.apache.org/dist/avalon/excalibur-i18n/jars/ http://www.apache.org/dist/java-repository/excalibur-i18n/jars/
-Mark
Leo Simons wrote:
Mark R. Diggory wrote:
Since Avalon is publishing distributions to both ibiblio and locally in
/www/www.apache.org/avalon/...
its the most "salient" project where there are now duplicate files between the java-repository and the dist/avalon directory
I will be glad to assist in finding a way to reduce this duplication. Two options I can think of are either
1.) avalon migrate its distribution process into java-repository/...
that will be immensely painful. We have lots of files (around 1100 or so?) and lots of symlinks among those. I really not want to break URLs if possible. Besides, we have existing release publishing scripts set up pointing to the current avalon distro location.
2.) we symlink the avalon projects into the java-repository/...
I like this one better. It should be possible to just do
cd /www/www.apache.org/dist/java-repository ln -s ../avalon/* .
We'll have to solve some naming conflicts (there probably are a few :D), but it is the least impact on avalon, the least work, and the least impact on the mirrors. I did this a long time ago for avalon-framework (as a test in setting up java-repository), and it worked just fine.
The only bit of maintainance that would come up every so often would be the addition of a symlink when we have a new first release of a project. Which is feasible to do, and possible to automate.
thanks, and as avalon is already working intensively with Maven, I hope you will find this migration effort beneficial.
+1. Thanks heaps for investing the neccessary time. I know its hard work! :D
-- cheers,
- Leo Simons
----------------------------------------------------------------------- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles & Opinions -- http://articles.leosimons.com/ ----------------------------------------------------------------------- "We started off trying to set up a small anarchist community, but people wouldn't obey the rules." -- Alan Bennett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-- Mark Diggory Software Developer Harvard MIT Data Center http://osprey.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
