I see what you mean. I'm ok with keeping this stuff to a minimum, deprecating in 1.1 and removing later - it's just that it means backporting the old functionality to the components :(
I don't think 1.1 or 2.0 would be that far off, but even so the worst case for users would be deprecation warnings, not anything they are forced to change. BTW, if JIRA is anything to go by, there are 30 or so bugs to fix by 1.0 that aren't slated for RC2, so we probably need one more RC. Other than that, the period and quarantine time sounds right. Cheers, Brett > -----Original Message----- > From: Maczka Michal [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 21 January 2004 7:31 PM > To: 'Maven Developers List' > Subject: RE: PROPOSAL: deprecate pom.id, dependency.id, > pom.currentVersion for Maven 1.0 RC2 > > > Brett, > Certainly I can understand your point of view and in silence > I am agreeing with it. My point is that god knows when 1.1 > will be out. Maybe it will be 2.0 and it will be released in > 2 years from now? Also it is rather undecided what changes > will be in this version and if it will be at all compatible > with 1.0. My expectation were that RC2 = 1.0 + two/three > weeks of "quarantine" to see if everything works. So it's > almost like we will be deprecating something directly in 1.0. > I would rather give those users who care about magic numbers > (1.0) something acceptably stable and usable > with all its current features without forcing them to ever > change to next generation of maven. > > > > Michal >
