I think you can just create a JIRA at [1] so that your dependencies will be uploaded in the public repository. The public maven repository is handled by the maven guys.
I guess another way is to make an archive of your local repository and store it in a publicly available location so that one can always rebuild the release if needed. I know maven has a feature to create this zip file, but I can't recall where. Cheers, Guillaume Nodet kelvin goodson wrote: > How can an Apache project robustly handle the situation where 3rd > party dependencies don't provide maven binary artifacts? In > particular, when an Apache release is made, we need to be sure that > the 3rd party dependencies are available for as long as the release is > available. > > Regards, Kelvin. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
