Phil Steitz a écrit :
Regarding package renaming, there are very few backward incompatible changes lined up for 2.0, and all of the proposed 1.5-dependent stuff is new, so I am hesistant to do a wholesale change. What would be the problem with renaming only packages that contain classes with incompatible changes?
On the other hand, a new package may not be needed at all. I checked on mvnrepository.com the number of open source projects depending on Commons Math, and besides a beta version of JET from Codehaus, there is none. That means slight incompatible changes in the 2.0 API are unlikely to cause a dependency havoc across hundred of projects.
Emmanuel Bourg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
