+1 The next Qpid Broker for Java is probably going to be 7.0 (i.e., a major release) so now is as good a time as any.
Some dates for reference [1]: Java Version First Release End of Public Updates 7 Jul 2011 Apr 2015 8 Mar 2014 Sep 2017 or later [1] http://www.oracle.com/technetwork/java/eol-135779.html On 09/01/17 22:28, Robbie Gemmell wrote:
I'd like to propose dropping support for Java 7 in the broker and both JMS clients in their next significant new releases. Almost a year ago, there was a proposal around preparing to end support for Java 7 in the broker and AMQP 0-x JMS client, with the the idea of doing a ~Q3 2016 major release in which the broker required Java 8, followed by a minor follow-up release in 2017 that then dropped support for the client. I believe both still currently retain support for Java 7. I agreed with the proposal and suggested something similar made sense for the AMQP 1.0 JMS client, and I think it is time we made that change. I think it would be appropriate to do so in concert with the 0.20.0 release the client is now ready for, and plan to do so unless convinced otherwise. While on the Java 7 subject: I'm a little more neutral about Proton-J, and wouldn't be that opposed to it continuing to for a bit longer, although probably not all that long, as the majority of builds I know of personally that depend on it already require Java 8, some doing so before Proton even dropped its Java 6 support in 2015 (after Java 7 went EOL). Robbie --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
