>-----Original Message----- >From: Kalle Korhonen [mailto:kalle.o.korho...@gmail.com] > >On Fri, Aug 6, 2010 at 10:43 AM, Haszlakiewicz, Eric ><ehas...@transunion.com> wrote: >>>-----Original Message----- >> I don't (yet) know much about the internals of maven, but is it really >> that much of an impact on the code? There's already support present for >> checking for differences in snapshot versions, right? I'm imagining >> that making it work for release artifacts would be a matter of not >> distinguishing between release and snapshot artifacts and having the >> check apply to both. >> It sounds like you think it'll be harder to do than that; what I am >> missing? > >What you are asking is absurd. That's the exact difference between >snapshots and releases; snapshots should be updated and releases >shouldn't. Why would you insist on removing this differentiation? >Wouldn't it be easier for you to just use snapshots if you need to >check for updates?
Please read the rest of the email thread. The short summary is: Yes, I know what *should* happen, but the world isn't perfect and release artifacts DO sometimes change. It is not absurd to be able to detect and recover from that kind of situation. eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
