Great,

Ok, its not exactly a 1 to 1 mapping, I suspect we need to figure out what maven project directory contians what from dist:

/www/www.apache.org/dist/java-repository>

avalon
avalon-activation
avalon-apps
avalon-composition
avalon-cornerstone
avalon-extension
avalon-framework
avalon-http
avalon-meta
avalon-phoenix
avalon-repository
avalon-util
cornerstone-connection
cornerstone-datasources
cornerstone-scheduler
cornerstone-sockets
cornerstone-store
cornerstone-threads
excalibur
excalibur-altrmi
excalibur-cli
excalibur-collections
excalibur-component
excalibur-concurrent
excalibur-configuration
excalibur-containerkit
excalibur-datasource
excalibur-event
excalibur-extension
excalibur-fortress
excalibur-i18n
excalibur-instrument
excalibur-instrument-manager
excalibur-instrument-manager-interfaces
excalibur-io
excalibur-lifecycle
excalibur-logger
excalibur-monitor
excalibur-mpool
excalibur-naming
excalibur-pool
excalibur-sourceresolve
excalibur-store
excalibur-thread
excalibur-util
excalibur-xmlutil
merlin
merlin-tutorial




/www/www.apache.org/dist/avalon>


avalon-extension
avalon-framework
avalon-meta
avalon-repository
cornerstone
cornerstone-connection-api
cornerstone-connection-impl
cornerstone-datasources-api
cornerstone-datasources-impl
cornerstone-scheduler-api
cornerstone-scheduler-impl
cornerstone-sockets-api
cornerstone-sockets-impl
cornerstone-store-api
cornerstone-store-impl
cornerstone-threads-api
cornerstone-threads-impl
excalibur
excalibur-compatibility
excalibur-component
excalibur-configuration
excalibur-datasource
excalibur-event
excalibur-fortress
excalibur-i18n
excalibur-instrument
excalibur-instrument-manager
excalibur-lifecycle
excalibur-logger
excalibur-monitor
excalibur-naming
excalibur-pool
excalibur-sourceresolve
excalibur-thread
framework
merlin
phoenix

In terms of whats on ibiblio. Were you already maintaining a separate maven repository there? I found a symlink in java-repository point off to the filesystem location fo this directory:

http://www.ibiblio.org/merlin/

Is there anything else from avalon over at ibiblio and outside of the following locations?

http://www.ibiblio.org/pub/mirrors/apache/avalon/
http://www.ibiblio.org/merlin/
http://www.ibiblio.org/maven/

thanks
-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


-- 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]



Reply via email to