Login  Register

Re: Upgrading from JOGL 2.3.2 to Current master for Java 11 support

Posted by Sven Gothel on Feb 07, 2020; 6:18am
URL: https://forum.jogamp.org/Upgrading-from-JOGL-2-3-2-to-Current-master-for-Java-11-support-tp4040335p4040345.html

On 2/7/20 6:08 AM, aldebaran30701 [via jogamp] wrote:

> 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.

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.

>
> 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

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