Of course this means that the maven team is imposing their idea of good process on the other apache projects like tapestry which was also impacted by this ...
I could understand this if the release occurs. (i.e. if 2.2 is released then the 2.2-SNAPSHOT could be reasonably expected to be discarded) part of the process of tracking down a bug involves going back to known states of the code. Using the snapshots to diagnose when a bug appeared is useful as people move toward a release.....something to think about. Just my 2c.... clearly I will need to isolate my project in the future from the official maven repos ... probably should do it anyhow but would have preferred to do it later.... -Pat On Tue, Aug 5, 2008 at 3:53 PM, Brian E. Fox <[EMAIL PROTECTED]>wrote: > The official answer is this: > http://www.apache.org/dev/release.html#what > > Technically only the development team should be using snapshots and it > seems like we should expect snapshots to be cleaned out on a more > regular basis. Therefore if you use them, you better have a repo manager > or some other way to isolate yourself. This is just plain best practice > anyway. > > -----Original Message----- > From: David Conde [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 05, 2008 8:20 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: what happened to the plugin snapshots.... > > Moving this onto the dev list. > > Are there plans to re-publish snapshots of these soon? I currently have > a dependency on maven-embedder which brings in wagon etc which cannot be > > resolved now. > > Thanks, > David Conde > > > > --------------------------------------------------------------------- > 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] > >
