Hi Sam,
Thanks for your replay, after removing the “unless=java.version.8” I can do a
proper build using java8 that works on the java8 jvm.
But this raise another question, is the plan officially release two versions of
Cassandra, one for Java8 and one for Java11?
/Tommy
On tis, 2019-06-11
Hi Attila,
I just realized that the build I was using was two weeks old, but now I have
double checked with the latest trunk and there is no changes in this area and I
get the same behavior.
One explanation might be that "artifacts" dosen't fail, if just do nothing due
to the
Hi All,
Just FYI
I did a Java 8 build (dist - to be more spcific, that involves $ ant
artifacts) from 4.0 trunk (after git pull) on Sunday morning (so 9th of
June) - there were no issues for me
I did it on both Windows and Linux (Debian) machines
Maybe there were commits since then.. I have
> On 11 Jun 2019, at 10:04, Tommy Stendahl wrote:
>
> Hi,
>
> I can't find a way to build 4.0 artifacts so I can run Cassandra using Java8.
> Building the artifacts ("ant artifacts" or "ant mvn-install") requires
> building with Java11 but since CASSANDRA-15108 the result is not Java8
>
No, this is not intentional. At the very least for 4.0 we are going to keep
compatibility with Java 8.
> On 11 Jun 2019, at 10:04, Tommy Stendahl wrote:
>
> Hi,
>
> I can't find a way to build 4.0 artifacts so I can run Cassandra using Java8.
> Building the artifacts ("ant artifacts" or "ant
Hi,
I can't find a way to build 4.0 artifacts so I can run Cassandra using Java8.
Building the artifacts ("ant artifacts" or "ant mvn-install") requires building
with Java11 but since CASSANDRA-15108 the result is not Java8 compatible
anymore, is this intentional or was this done by mistake?
