Upgrading from JOGL 2.3.2 to Current master for Java 11 support

I am working on migrating to Java 11, and have to upgrade the JOGL dependent libraries.

From my understanding, If I use the most current, I have to build from binaries. I've been following the steps religiously on https://jogamp.org/jogl/doc/HowToBuild.html for building Gluegen and Jogl, but keep facing the same error after multiple attempts.

These are the steps I've taken.
1. ensure my cmd or git bash sees ant, java home etc.
2. cloned the git repository from (Because https://jogamp.org/cgit/gluegen.git/ did not work) with --recurse-submodules
    a. https://github.com/sgothel/jogl
    b. https://github.com/sgothel/gluegen
3. ensured the structure was as follows
jogamp
    |
    -- jogl
    -- gluegen
Where the clone command created the folders jogl and gluegen
4. set CLASSPATH=
5. loaded cmd within gluegen/make
6. executed `ant -Dtarget.sourcelevel=1.8 -Dtarget.targetlevel=1.8 -Dtarget.rt.jar=/your/openjdk8/lib/rt.jar`
Build failed. See attached log text for output with -v flag.

I'd love some advice or guidance on what I can trial next. Or if I misunderstood something.
Cheers, Aldebaranjogl_build_log.txt

Hello

Why not using the latest RC build of JOGL 2.4.0 in the meantime?

Actually, "package jdk.javadoc.doclet does not exist" indicates that you're using Java < 9 to compile.

On 2/6/20 1:10 AM, aldebaran30701 [via jogamp] wrote:
To double check, I just did the following on GNU/Linux (Debian 10),
which includes

'git version 2.20.1'

and

openjdk version "11.0.6" 2020-01-14

git clone --recurse-submodules git://jogamp.org/srv/scm/gluegen.git gluegen
cd gluegen/make
ant -Dtarget.sourcelevel=1.8 -Dtarget.targetlevel=1.8
-Dtarget.rt.jar=/opt-linux-x86_64/jre1.8.0_121/lib/rt.jar

So the git clone w/ recursive submodules does work.
Our build server are also using the very same setup.
Curious.

~Sven

So I ensured JAVA_HOME was set to the correct version which it was, but then also checked path. Path did not include the JAVA_HOME. It had a direct path variable to an old version of java. I fixed that.
It got further into building.

I then had an issue of no GCC compiler, so I installed MINGW and then downloaded the dependencies for GCC.
It built even further but errored on GAWK not found.

I built again with -d -v tags and for some odd reason it was successful this time.

This is unrelated to the above issue, but if I wanted to use something like Ivy to download the dependencies, would I be able to point it to the web page showing releases like this? https://jogamp.org/deployment/archive/rc/v2.4.0-rc-20200202/
Currently it uses ivy to download from maven central, but your most recent version 2.4.0 is not on maven. Any suggestions for other ways to do it without having to host my own repository or manage the files locally with the project?

TLDR; I need to upgrade, but the newest version is not on maven to just change the dependency pointers

On 2/7/20 6:08 AM, aldebaran30701 [via jogamp] wrote:
It is rather odd that after religiously following my build descriptions
you had these issues. However, glad to read that it works our after
these minor hiccups. Welcome.

Aldebaran, the following is not necessarily intended for your eyes,
especially not if you are merely a non-commercial user.
However, I need to set some curious expectations straight here.

Companies are very welcome to inquire for commercial support requests
<https://jogamp.org/wiki/index.php/Maintainer_and_Contacts#Commercial_Support>
as this project can only be maintained by paying parties.

Otherwise there is no 'TL;DR' here to see for me or other developers.
Maven'sh builds will be provided when they are provided
and we are not on a call by fellow users :)

But what we do achieve is to produce a very reliable product across platforms,
which maybe used by anyone free of charge AS-IS
and for which companies are more than welcome to pay for support.

On another positive note, it is not our biz model to collect any data from
our users and monetize these. No GOOG nor IntelliJ effect to see here ;-)

Best regards,

~Sven

Much appreciated with all the help thus far Sven!
If I wanted to decompile, and then recompile to .jar from the 2.4.0 rc version, to add the code at the last comment of this thread (http://forum.jogamp.org/canvas-not-filling-frame-td4040092.html)
Would I follow the build steps outlined in the how to build? I want to trial a fix to get the application I am working on to work when scaled in windows without the offset.

Regards,
Aldebaran

Maybe a much better solution would consist in trying to agree on a fix if something is still broken so that the next release candidate will contain it without the need of building JOGL on your own (even though it would be interesting to understand why you can't build it).

By the way, I already modified the class file of GLCanvas to make a patched version of JOGL at least once...

On 2/11/20 9:57 AM, gouessej [via jogamp] wrote:
> Maybe a much better solution would consist in trying to agree on a fix if
> something is still broken so that the next release candidate will contain it
> without the need of building JOGL on your own

Indeed. Still, for him to fix it properly, he would still need to build.
But .. good news everyone:

Since I finally have been known which issue we are talking about,
please notice that Bug 1374 has been reopened
<https://jogamp.org/bugzilla//show_bug.cgi?id=1374#c3>.

In general all High-DPI issues shall be fixed for 2.4.0 release
<https://jogamp.org/wiki/index.php?title=SW_Tracking_Report_Feature_Objectives_Overview#High_DPI>.

I will add a remark to the forum issue as well.

> (even though it would be
> interesting to understand why you can't build it).

Puzzling indeed.

~Sven

(email didn't work, hmm)

On 2/11/20 9:57 AM, gouessej [via jogamp] wrote:
> Maybe a much better solution would consist in trying to agree on a fix if
> something is still broken so that the next release candidate will contain it
> without the need of building JOGL on your own

Indeed. Still, for him to fix it properly, he would still need to build.
But .. good news everyone:

Since I finally have been known which issue we are talking about,
please notice that Bug 1374 has been reopened
<https://jogamp.org/bugzilla//show_bug.cgi?id=1374#c3>.

In general all High-DPI issues shall be fixed for 2.4.0 release
<https://jogamp.org/wiki/index.php?title=SW_Tracking_Report_Feature_Objectives_Overview#High_DPI>.

I will add a remark to the forum issue as well.

> (even though it would be
> interesting to understand why you can't build it).

Puzzling indeed.

~Sven