We definitely do not want to remove JDK 8 support for 5.16.0 so my vote is for option 1. I think it's fine if we build with JDK 8 as long as it supports JDK 8 - 11 at runtime.
For 5.17.0 we can work on building with JDK 11. For one thing I think we should just make it easier on ourselves and remove LevelDB entirely as it has been deprecated now for several major versions and there isn't any reason to keep it at around at this point. On Tue, Jan 28, 2020 at 7:58 AM Jean-Baptiste Onofré <[email protected]> wrote: > Hi guys, > > I would like to move forward on ActiveMQ releases: > > - ActiveMQ 5.15.12 > I'm preparing several dependency updates and important fixes on the > activemq-5.15.x branch. It includes some security fixes, postgresql jdbc > store performance improvements, ... > I have some PRs under review and on the fly, so, I plan to submit > 5.15.12 to vote next week. > > - ActiveMQ 5.16.0 > I did a full pass (standalone and in Apache Karaf) with JDK 11. The > broker works without problem, including on Karaf 4.2.8. > However, it's not currently possible to fully build with JDK 11. I have > a branch where I did the required changes (remove the use of tools.jar > in openwire generator, add annotation and jaxb dependency in different > modules, update scala for leveldb, ...). > The question that I have is about what's the exact target for 5.16.0: > 1. We still build ActiveMQ 5.16.x with JDK8, but it supports both JDK8 > or JDK11 at runtime. > 2. I do the changes required to build with JDK11, and then we will only > support JDK11 at runtime. > Thoughts ? > Anyway, I would like to submit 5.16.0 to vote asap, so please, let me > know what you think about JDK support (build or/and runtime). > > Regards > JB > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
