On Tuesday 07 June 2016 15:24 Benedikt Ritter wrote: > Hi, > > sebb <seb...@gmail.com> schrieb am Di., 7. Juni 2016 um 11:49 Uhr: > > 0) I think we are fairly close to being able to release compatible > > code with all the necessary fixes > > > > 1) I don't believe we should force users to migrate their code in > > order to support java 7/8. > > In the case of Findbugs, this would also require all detector plugins to > > change. > > > > 2) the BCEL6 redesign has barely started. yes, some minor changes have > > been done to tidy the code, but nothing has been done to the original > > design, which is full of mutable classes and non-private mutable data. > > I think a lot more needs to be done to produce an API which will be > > sufficiently stable. > > Otherwise there will soon be another API break. > > > > I'm okay with the 5.3 release. But right know it feels like you're the only > one wants to go through the trouble.
What trouble do you mean? BTW if I can help testing, I'm ready to go. > I propose we create the 5.x branch now. Those who want/need a compatible > release can work that out in that branch. All others can work on trunk to > get BCEL 6 out of the door with Java 7 and Java 8 compatibility. Sorry, IMHO the *only* reason to release 5.3 after many years *IS* the Java 7/8 compatibility. We (user) just want something stable we can use on a modern JVM (and Java 7 is already *obsoleted*!), nothing more. Before thinking about new API's, please just release something running on Java 7/8. -- Kind regards, google.com/+AndreyLoskutov --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
