I've found difficult to compile everything for all supported platforms. Usually, I compile only under one of them at a time. Pushing things into Maven Central doesn't seem to be trivial, Martin seems to be a lot comfortable than me with that. My suggestions are these furthers:
- Use Gradle with Ant in order to simplify building a bit. Gradle can be used to put releases into Maven and as it can work with Ant, it doesn't force us to drop Ant especially where it does a better job. Personally, I find Maven as a build tool not flexible enough for our kind of project.
- Provide a solution to allow contributors to make test builds. For example, I need to test a tiny change in GLContextImpl, I commit into a separate branch, a CI/CD server builds JogAmp with my change, I take the JogAmp fat JAR and I use it in my TestNG unit test to ensure that my fix really works, the server runs our tests on all supported platforms too. Maybe it's already possible right now, maybe I'm missing something.
- Drive some parts of JOGL easier to modify without recompiling, for example adding renderer quirks, adding an alternative input manager (I really need
relative mouse movement management for T.U.E.R)
- Support Foreign Function and Memory API, a memory segment created with it should be usable instead of a NIO buffer. It's not mandatory as you can create a NIO buffer from a memory segment in the meantime. If things go well, maybe this API will be suitable to do many things in Java without JNI.
- WebGPU, WebAssembly, Java to web transpiling... I don't promise to succeed but I'm on it.
I agree with having a meeting.
By the way, I can't update the tickets in Bugzilla, I get the following error message:
Invalid Content-Type 'subtype' parameter at Bugzilla/BugMail.pm line 499.
For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error.