+1
To clarify, we already "support Java 7".
I believe it is fine to drop support for Java 6 in the same time frame
as jclouds (i.e. early 2015). I've checked this with some enterprise
customers, and they are fine with it. If any other customers feel
strongly that Java 6 support is important then please shout out!
Aled
p.s. to-date, this is a much bigger issue for jclouds because that is
used as a library in other people's code; brooklyn has so-far been used
predominantly as a stand-alone process, even though one can also use it
as a library.
On 14/10/2014 09:17, Andrew Kennedy wrote:
Andrea, Hi.
I think we should also support Java 7, most of the time I'm building
Brooklyn using it and there are no issues. Additionally, it would be
nice to use some of the new features from 7, although lambda's would
be even better ;)
Andrew.
--
-- andrew kennedy ? cloud engineer : http://blog.abstractvisitorpattern.co.uk/ ;
On 13 October 2014 23:20, Andrea Turli <[email protected]> wrote:
Hi,
I'd like to share a concern here about one of our dependency. As far as I
can tell jclouds 2.0.x is going to support only java7: what kind of impacts
do you see for Brooklyn, when we'll need to adopt jclouds 2.x ?
Best,
Andrea
Andrea
