Posted by Sven Gothel on Jan 25, 2020; 10:06am
URL: https://forum.jogamp.org/Where-is-the-latest-version-of-Java3D-tp4040278p4040295.html

On 1/25/20 6:38 AM, philjord [via jogamp] wrote:
> Ok thanks, I've pushed it to dev 1.7.1 now.
>
> There's a few really good pull requests from Egor
> <https://github.com/etsinko> that will be in dev 1.7.1 shortly.
thank you Phil.

>
> I've updated the deployment directory so 1.7.0-final now exists
> <https://jogamp.org/deployment/java3d/1.7.0-final/>.
thank you
>
> Harvey getting the search results is fair, I haven't done anywhere near the
> work he has done, but possibly in the future google will notice activity on my
> account...
Everybody is helping out as they can and thank you for maintaining j3d now.

>
> I'll update the jogamp wiki and maintainers page to make it more obvious that
> I should be the main contact.
thank you.

> We could put a java3d fork into the jogamp
> github repo to indicate which is the main java3d repo, I guess, that would be
> more Sven call than mine.
I 'personally' only consider JogAmp's SCM as canonical,
but you are correct - I will and shall add this to github jogamp as well
and you would then need to push to that backup storage space too.

I just forked following repos from 'philjord' -> 'JogAmp'
- vecmath
- java3d-core
- java3d-utils
- java3d-examples (Phil, please add this to JogAmp's SCM as well)

I also gave philjord admin/owner access to all
of the JogAmp team on github, as we never created fine grained roles
over there. This is more than OK, as it only is a backup storage.
On JogAmp we have fine grained access control.

Now it is all up to Phil to keep these repos in sync.

>
> Another option might be to publicize that scm on jogamp
> <https://jogamp.org/cgit/java3d/java3d-core.git/> should be seen as the latest
> version (which is of course a copy of my github repo)
Everything will be, by definition,
a copy of j3d's maintainer (Phil now) maintained j3d repo of JogAmp :)


>
> Once again, thanks for looking into this and actually providing the bug
> reproduction and fix in full.

Thanks to all collaborating, past, present and future.

Yes, I need to follow up with the Maven work 'soon'.

Planned after I fixed all the SWT and High-DPI issues for 2.4.0 release.

In the meantime it should be possible to build JogAmp's j3d
using either: RC aggregated builds or local source builds
- jogamp/gluegen
- jogamp/jogl
- jogamp/vecmath
- jogamp/java3d-core

.. etc etc

If this is not possible today, I recommend to add this build feature.

Below I elaborate a little bit on these 'pull resources' features,
so you may stop reading here.

Cheers, Sven

...

IMHO it is very essential to build things using a manually maintained
and pulled version of dependencies,
not relying on 'some infrastructure of others'.

Might be b/c I am 'an old dog', but my experience has told me
to always keep a safe option open.

Today, whether it is gradle, maven or whatever, they might pull-in the world
as dependencies to build 'Hello World' :)

This *might* be OK, but nobody can really tell and nobody is able to give
their right arm for this convenience.
I don't argue that such convenience is indeed very convenient and hence nice
to speed up building projects, but if you are building a mission critical
application this might not be what you want :)

One reason why it might come in handy to have one maven'ish build-view
and one traditional build-view.

A project's security level has a inverse correlation to the number of
dependencies, this includes the tools to build the beasts.

~Sven