On 4/11/07, John Casey <[EMAIL PROTECTED]> wrote:
Actually, the "unwittingly try and build it with 2.1" scenario is a case where it would be nice to have a prereq on maven < 2.1 in the POM. I don't think that 2.0.x supports that sort of thing in the <prerequisites> section, but I imagine the enforcer-plugin would do it.
Turning this idea around, wouldn't it be possible to force an update of the POM to make it compatible with 2.1 ? That way, people cannot use 2.1 without willingly marking their POM. Those who build a project made for 2.0.x with 2.1 get an error or warning. Probably not for a 2.x release, and probably not wanted as not completely backwards compatible but just an idea. J --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
