I really appreciate the work that has been done on the Java3d library. I would like to ask if the jogamp organization could put their java3d artifacts and jogamp fat jar (or something equivalent) in the Maven Central Repository. I downloaded the java3d libraries from https://jogamp.org/deployment/java3d/. Version 1.7.1 works fine for me.
I hope for your reply. Thanks in advance,
I got a long way towards this about 2 years ago, but somewhere between me and Sven the process stopped, I can't recall why, but I need to publish under org.jogamp so I need Sven to do something on I third party site to verify me or something (was it called sonique?)
I'll dig through my emails and see if I can get the process started again.
If you can't put it into Maven Central yet, we could put it into the JogAmp Maven development repository in the meantime as we do for JogAmp and soon for JogAmp's Ardor3D Continuation too:
If this solution pleases you, ask Sven to create a sub-directory named "maven-java3d" with the convenient rights.
Thank you Juilen, I don't care if the artifacts are in the Maven Central or in any other repository.
I've just sent a private message to the administrator Sven Gothel, I think you were referring to him.
Yes. Maybe my suggestion is not accurate enough. I suggest Phil to publish the snapshots and possibly the released versions into the JogAmp Maven development repository, doing the same on Maven Central only for released versions would be a second step. If and only Phil agrees with my suggestion, Sven will have to create a separate directory to store Java3D artifacts.
Ideally, other JogAmp projects should do something similar to ease the use of our APIs with Maven compatible tools including Maven itself, Gradle, Ant, etc. Moreover, storing third party dependencies into versioning systems isn't very smart, it drives the checkout uselessly slower.
Personally, I won't upload anything on Maven Central. Using our Maven repository as a first step has a lower barrier of entry (no subscription or administrative step required beyond creating a directory) even though some developers refuse to use dependencies not coming from Maven Central.
Phil will have to run those command lines (more or less, needs to be adapted to a project not using Gradle):
scp -r /home/philjord/.m2/repository/org/jogamp/java3d email@example.com:/srv/www/jogamp.org/deployment/maven-java3d/org/jogamp/
First of all, I will not work on pushing things into the maven maven repo,
but in case anybody is willing to handle the non-jogamp maven repo for any project,
please feel free to do so.
Hence, the below is for our jogamp maven repo ...
Then - again - I am not a maven expert.
If there is a much better way maintaining our own maven repo than these scripts,
go ahead - show me - and I will also give you ssh access rights and ability to publish on jogamp.
Julien showed one easy way to sort of push a local maven cache to our jogamp maven repo
with Ardor3D .. if that is satisfactory for you, its good with me.
I gave both folders write access and ownership to the java3d group,
which Phil and Julien belong to:
Up to the java3d folks to chose a maven strategy (the jogamp-scripting thingy or anything else).
Please tell me if you need anything else or whether I shall do something.
thank you for your reply. What I'm asking is very simple: just put the maven artifacts of j3dcore.jar, vecmath.jar and j3dutils.jar version 1.7.1-build-20200222 on your destination https://www.jogamp.org/deployment/maven-java3d/, which is now present and accessible (albeit empty). The artifacts I'm interested in are the ones at https://jogamp.org/deployment/java3d/1.7.1-build-20200222/. To do a good job, it is important to produce the pom.xml files for these artifact. A rather simple way to do it, if you have SSH access to the target file system, is to use maven itself, by running the commands:
If you HTTP server allows POST and PUT methods, instead of using SCP you can upload the artifacts using http / https protocols, which are natively supported by maven. In that case you don't need the fake pom.xml file.
Hope these hints will help you. Best regards,
I totally understand that each people has her/his own constraints, it's volunteer work after all, don't be sorry, it's ok. If you use "install" or "package" with Maven, you should obtain a similar result without using Gradle to publish your version locally before uploading it.
Thanks for offering to copy the files up, I've managed to carefully follow the great instructions provided and got the jar and pom files deployed to
Tomorrow I'll test a clean build to make sure they get pulled down correctly.
I notice you mention the repositories tag in maven, but you don't use it in any of the published pom files for ardor3d, where should that go?
Phil, Sven, Julien, thank you very much for your effort. It's now very easy to use Java3D in a complex maven project, without the need to manually download and install any dependences. Best regards, Riccardo.