> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 14 November 2003 04:35 > To: 'Maven Developers List' > Subject: RE: [VOTE] Make groupId mandatory for POM version 4? > > > What kind of deprecation period were you planning? > > I would suggest that we don't finalise POM v4 until 1.1, and both v3 and > v4 > should be loadable. If we decide to remove v3 support in the future to > simplify it, that's probably a decision for the time. > > It would be good if there were a stylesheet that could be applied to v3 > POM's to make them v4 (and any additional parameters just need to be > listed > at the end as required). > > Eg. maven pom:upgrade loads POM, sees it is v3, applies v3 -> v4 > stylesheet > that converst id to artifactId, warns there is no groupId and type, ...? > > Should be easy to implement. If not by a stylesheet, then some java code > that reuses the v3 loading code, and then has an pom4.createFromPom3 or > something.
Yes, just be careful that we shouldn't do this on plugins as they will become unusable in Maven rc1 or earlier. Which reminds me that we still haven't fixed the issue of saying what version of Maven a plugin is compatible with (no, I really don't like adding a <dependency> on Maven in the plugin... :-)). Would a solution be another new optional POM tag like <mavenVersion>: <mavenVersions> <mavenVersion>1.0-rc1</mavenVersion> <mavenVersion>1.0-rc2-SNAPSHOT</mavenVersion> [...] ? Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
