Open cstamas opened 6 years ago
Demo project reproducing this behaviour https://github.com/cstamas/lifecycle-1-13-4-compiler
Does the project build in the latest Eclipse 4.8 milestone? Eclipse JDT developers stated on several occasions they do not consider raw type support a priority, so I would not be too surprised there was a change in behaviour between Eclipse 4.7 used by lifecycle 0.13.3 or 4.8 used by lifecycle 0.13.4.
Tested Eclipse 4.8M5 with https://github.com/cstamas/lifecycle-1-13-4-compiler (having takari lifecycle set to 1.13.3 to make build pass), and same compilation error is reported.
Guess you can petition eclipse jdt devs to improve raw type support. Keeping this issue open for future references, but there is not much we can do from takari lifecycle side of things.
Env: OS: MacOS 10.12.6 Java version: 1.8.0_161 Oracle Maven: 3.5.2 Lifecycle config:
Symptom: Justby updating from lifecycle 1.13.3 to 1.13.4 (no other change!) the project fails to build w/ compilation error. Downgrading back to 1.13.3 makes project build just fine again.
This might be related to new compiler? As there is no source/target nor Java version change, merely the lifecycle plugin version is changed between builds. Or is there some language level mishap? Or just compiler configuration mishap? Please help where to look more.
The classes in question are these:
Where
GraphTraversalSource
comes from gremlin-core:3.3.1,MingTraversalSourceDsl
is insrc/main/java
andMingTraversalSource
is generated. I verified that 1.13.3 and 1.13.4 generates equal source files, no change there. Note:TraversalStrategy
is raw class.This is the most I can get out from build (w/
-X -e
):