On Aug 6, 2010, at 2:58 PM, Paul Benedict wrote: > On Fri, Aug 6, 2010 at 2:53 PM, Haszlakiewicz, Eric > <[email protected]>wrote: > >> You're missing the point of what I'm asking. I'm not suggesting that >> maven make it possible or easy to *create* the violation. I'm >> suggesting that it should be able to *detect* the violation. >> >> I'm baffled as to why the maven community is so against the idea of >> having additional (optional) checks to detect problems. >> >> > Eric, > > The point is releases don't change. To "detect" means wasting bandwidth > comparing your supposedly unchanging released local artifacts to supposedly > unchanging released remote artifacts. If anything, writing a Maven plug-in > for this would be more appropriate, but I don't see your suggestion as part > of Maven core.
And actually, it wouldn't be that hard to write such a plugin. But you have to want it... -K --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
