Snapshots are a very good thing for internal development. It would be impossible to manage my builds without them. I think that people using snapshots of plugins are a symptom of another problem -- long release cycles. Just because people do bad things with snapshots doesn't mean snapshots should go away.
It already takes a little effort to get at them, the snapshot repo isn't part of the super-pom, so if you go out of your way to get them, you should understand the consequences. It's like me picking up an unstable version of some jar and then complaining that it broke later and asking the creators to stop releasing unstable versions at all(that are clearly marked as such). People would then just go get the code anyway. -----Original Message----- From: Kevin Menard [mailto:[EMAIL PROTECTED] Sent: Thursday, April 12, 2007 1:09 PM To: Maven Developers List Subject: RE: Remove auto-resolution of plugin versions from Maven 2.1 Right. My point is that regardless of what the original intention may have been, the current process facilitates laziness via SNAPSHOTs. Without them, incremental builds would be necessary, which would give fixed version numbers with known binaries. If the plan is to take actions to help prevent users from having things break on them, this may be easier than the path you outlined. -- Kevin > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
