Michal, That was exactly my point. Let the users of 1.0 continue to use what they have, but also let them use the new versions now rather than cutting them off at the knees for 1.1 :)
It's only a deprecation at this point, not a removal. Cheers, Brett > -----Original Message----- > From: Maczka Michal [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 20 January 2004 7:05 PM > To: 'Maven Developers List' > Subject: RE: PROPOSAL: deprecate pom.id, dependency.id, > pom.currentVersion for Maven 1.0 RC2 > > > > > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, January 20, 2004 12:05 AM > > To: Maven Developers List ([EMAIL PROTECTED]) > > Subject: PROPOSAL: deprecate pom.id, dependency.id, > pom.currentVersion > > for Maven 1.0 RC2 > > > > > > Hi, > > > > I was wondering whether everyone agrees to accepting, but > > deprecating these > > tags in the next Maven release, in favour of pom.artifactId > > (whose behaviour > > will be corrected), pom.version and dependency.artifactId/groupId. > > > > +0 > > as I am fully agreeing with all those changes but I think > that it's generally not the best moment for changing POM - we > are about to > release RC2 > which I hope will be closely followed by 1.0. > > > Michal > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
