+1 to what Brian said. According to Apache policy, USERS should NOT be relying on Apache snapshot or any Apache builds that have not been properly voted on. Don't push the issue or furthur lock downs are likely. (they started discussing the idea of requiring apache username/password to access the snapshots even)
Basically, if you find you need to start using a plugin snapshot, you also should start pestering the maven folks to get it released. Even better, help out by submitting patches for any of the remaining issues. The sooner the issues get resolved, the sooner we can get releases made. Also, if you start submitting patches and bugging everyone, you're likely to be voted in as a committer and then you can do your own releases. That's how a lot of us became Maven committers. We annoyed the existing committers with patches and stuff enough that they voted us in just so we would stop annoying them. :-) Dan On Wednesday 13 August 2008 9:24:12 am Brian E. Fox wrote: > On 8/13/08 8:20 AM, "nicolas de loof" <[EMAIL PROTECTED]> wrote: > > The option is to allow timestamp for SNAPSHOT dependencies, considering > > the timestamp jar will not be updated as a SNAPSHOT would, and so the > > build get's reproductible ... until the snapshot repo gets cleaned ! > > > > The idea is interesting as we hardly get plugin releases, and have no > > roadmap for them, so a project that requires a bug fix has no other > > option > > No, it might be interesting for corporate use, but _definately_ not for > Apache use. > > Sounds like you haven't followed the infra threads regarding the use of the > snapshot repo. Specifically it is apache policy that snapshots be used for > the development team only as they are not sanctioned releases. Any attempt > to implement something like this to make it easier/ more reliable to use > Apache snapshot artifacts will likely result in further lockdown of the > Apache snapshot repo. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
