Epic bump.
As per https://issues.apache.org/jira/browse/PROTON-935 the build is
currently broken again on Java 6. We need to either update it to
compile on Java 6, since that is still the builds compiler
source/target, or alternatively drop support for Java 6 and require
Java 7.
I'd do the
+1 for dropping Java 6 from future releases.
On 07/08/2015 09:59 AM, Robbie Gemmell wrote:
Epic bump.
As per https://issues.apache.org/jira/browse/PROTON-935 the build is
currently broken again on Java 6. We need to either update it to
compile on Java 6, since that is still the builds
I'm +1 on dropping Java 6.
--Rafael
On Wed, Jul 8, 2015 at 6:59 AM, Robbie Gemmell robbie.gemm...@gmail.com
wrote:
Epic bump.
As per https://issues.apache.org/jira/browse/PROTON-935 the build is
currently broken again on Java 6. We need to either update it to
compile on Java 6, since that
Ok, I have updated the pom file to use Java 7 for the compiler source
and target, and updated the remaining jobs on the ASF Jenkins CI to
also use Java 7 (having changed the deploy job previously because
Java6 isnt able to work with the recent new SSL proxy).
Currently still failing due the tests
Hi all,
With Qpid 0.30 we have made the move to requiring Java 7+. Currently,
proton still allows for use of Java 6, so I wonder what peoples thoughts
are on the timing of a similar move for Proton? I'd personally like to do
it soon since Java 6 is EOL, but if not then I think we should at least
This is just testing... can't you have a java7 tests folder? you would be able
to still have java7 specific tests.
On Sep 24, 2014, at 7:13 AM, Robbie Gemmell robbie.gemm...@gmail.com wrote:
Hi all,
With Qpid 0.30 we have made the move to requiring Java 7+. Currently,
proton still allows
The compilation issue I missed in the patch was test-only this time, but it
could have as easily been in non-test code. The other tests now failing
might actually point to some functionality under test not working under
Java 6 at runtime though, which is more of an issue. If the tests showing
it
