Closed tommyettinger closed 5 years ago
Yep, I can sorta fix this by using Java 12 to build, but there will be a looming recurrence of this bug when Java 13 is released. Feel free to close this if you don't intend to support Java 13 or don't need this open while Java 13 is a ways off in the distance.
Hi @tommyettinger. Java 13 is a bit soupy at this stage. I'll probably let it bake another month or so before integrating it with manifold. DastardlyLands looks like a fun project!
I'm having other, weirder issues but I suspect they may be fixed by using the Java 8 setup. I'll post a different issue if I keep encountering trouble with setup; this one should probably stay focused on Java 13.
@tommyettinger Closing this issue as the root cause is Java 13 EA. Please file a separate issue if you experience problems using a supported JDK. Thanks!
Just to note: everything works great with Java 8 now. I haven't used modules at all and it doesn't look like I was opting out of the module system correctly when I tried Java 12 (JSON files were put in strange random-seeming modules like javax.security
when I didn't have a module-info.java
file). On Java 8 everything is working, classes are generated seamlessly from JSON, it's really quite nice.
Describe the bug When Manifold has been added as a dependency and annotation processor to a Gradle 5.4 project, even without any code importing Manifold, there is an error initializing Manifold and the project won't run any tasks. The project is DastardlyLands, it has multiple Gradle modules,
core
has the Manifold-related deps, andgradlew lwjgl3:run
will try to launch the app.To Reproduce Steps to reproduce the behavior:
Expected behavior Not a crash during compilation, pretty much any other outcome.
Desktop (please complete the following information):
Additional context It's entirely probable this is related to Java 13. The lines:
and
are probably relevant.
Stack trace