On Aug 6, 2010, at 1:00 PM, Haszlakiewicz, Eric wrote: >> -----Original Message----- >> From: Kalle Korhonen [mailto:[email protected]] >> >> On Fri, Aug 6, 2010 at 10:43 AM, Haszlakiewicz, Eric >> <[email protected]> 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, you're not going to win this one. It's part of the philosophy of Maven. It's also good practice. Give it up. I'm not going to fight the site generation being split out of Maven. I think I understand Jason's point on that, though I disagree. And that's a *much* less nasty violation of Maven's perceived function, if in fact, it is a violation. What you're wanting is a violation. -K --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
