On 8/23/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote: <snip/>
I tried to be careful in phrasing that, but didn't have much success ;-) Ofcourse, setting a m2 repository in personal webspace will be no fun (and a waste of time), but just posting the artifacts there (not in any particular repository layout) might be possible.
<snap/> Seems cocoon had a "staging" repo in personal webspace ;-) (see repository@ post a few minutes ago). Anyway, the other alternative would be to have an ASF wide test/staging repo, if at all that is possible. -Rahul
For simplicity, lets say we have a simple project which produces just one artifact, foo.jar (yes, I oversimplified!). I can do a "mvn compile" and scp foo.jar (with sums and sigs) to ~rahul. If folks think its OK (they will have to deploy manually to local repo), we deploy to the remote repo(s) of choice. I claim that the extra effort required to manually deploy the artifacts in the local repo (by folks who are testing it) actually works in our favor, since there is little chance to accidently acquire the artifact (as against the apache snapshot repos, which are fairly "well-known") and thereby, forget to replace it with the "final" v1.0.3. -Rahul
