Thanks Brett,
I'm just concerned as well, that there may be distributions out on Apache the reference the ASF Repository jars directly instead of using Ibiblio or dyncloser.cgi. If those projects have been shortsighted in releasing distros's that have dependencies on interim releases in java-repository, then my proposed changes will effect them.
I think I will be moving forward with this proposal. As well as deleting these files, I will build a log of all the changes so that recovery from the archives can occur if any problems arise. It seems more important that we get the repository properly organized and structured than maintain old external project dependencies on unsanctioned interim releases in java-repository.
-Mark
Brett Porter wrote:
Hi Mark,
I think this is just a miscommunication, as what you have said below is what all the projects do
1.) In Maven project.properties, Referencing the remote repository
maven.repo.remote=http://www.apache.org/dist/java-repository/
2.) In Maven project.properties, Referencing a central repository
maven.repo.central.directory=/www/www.apache.org/dist/java-repository
3.) In Ant files generated from Maven, Hardcoded references to java-repository.
I believe we should take the following stance on these cases:
1.) ----1 !!!
2.) +1
3.) ----1 !!!
I agree.
As well, most projects that have java-repository as a remote repo, also have have ibibilio in from of it:
If I ever reference java-repository, its not in an automated fashion, and always behind dyncloser.cgi (eg, the release announcements).
- Brett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
