commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <>
Subject [BCEL] 5.3 is going to be messy
Date Mon, 06 Jun 2016 19:44:21 GMT
Hi all,

I had a brief look at the state of BCEL wrt doing a last 5.x release. Well,
it feels like that is going to be a mess:

- We have @since 6.0 annotations all over the code.
- We have same deprecated classes - why if the code is currently in the
shape for the 6.0 release, there should be no deprecated stuff
- We have chances.xml which are talking about the next big 6.0 release.
- We have renamed package coordinates which make it hard to generate a
Clirr report.

This will all have to be resolved before we can do the 5.3 release. I'm
currently wondering what might be the best way to push out the 5.x release.
I think we should create the 5.x branch ASAP, so that the way is free for
work on the important stuff in trunk. Hopefully this will enable us to
implement the missing bits for Java 8 support and get the 6.0 release out
of the door soon.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message