processing-core-4
processing-core-4 copied to clipboard
Missing Required JogAmp Repo
Current build requires org.jogamp.gluegen:gluegen-rt-main:2.5.0-rc-20230523, which (apparently) isn't available from maven central. Adding the jogamp maven fixes it, (kinda).
maven {
url=uri("https://jogamp.org/deployment/maven/")
}
Is this addressable upstream?
Could not find org.jogamp.gluegen:gluegen-rt-main:2.5.0-rc-20230523.
Searched in the following locations:
- https://repo.maven.apache.org/maven2/org/jogamp/gluegen/gluegen-rt-main/2.5.0-rc-20230523/gluegen-rt-main-2.5.0-rc-20230523.pom
- https://jitpack.io/org/jogamp/gluegen/gluegen-rt-main/2.5.0-rc-20230523/gluegen-rt-main-2.5.0-rc-20230523.pom
Required by:
project : > com.github.micycle1:processing-core-4:4.3
The repo's pom (Maven) already includes the jogamp repository:
<repositories>
<repository>
<name>jogamp</name>
<id>jogamp</id>
<url>https://jogamp.org/deployment/maven/</url>
</repository>
</repositories>
Are you using Gradle? I wonder if Jitpack doesn't handle the Maven repository definitions when used as a Gradle artefact.
Actually, the 4.3 artefact had jogl at 2.5.0-rc-20230523 as you stated; 2.5.0 was in main branch only.
I've re-released 4.3 as 4.3.1. The build now includes JOGL at v2.5.
However, it should have still worked for you, as 2.5.0-rc-20230523 exists here:https://jogamp.org/deployment/maven/org/jogamp/jogl/jogl-all-main/2.5.0-rc-20230523/. I still think there's a problem with Gradle (see https://github.com/micycle1/processing-core-4/issues/9 also).
The repo's pom (Maven) already includes the jogamp repository:
<repositories> <repository> <name>jogamp</name> <id>jogamp</id> <url>https://jogamp.org/deployment/maven/</url> </repository> </repositories>Are you using Gradle? I wonder if Jitpack doesn't handle the Maven repository definitions when used as a Gradle artefact.
Yes, using gradle. There are some other issues with this as well, including the underlying dependencies for jogl not being resolved. Might make a PR with gradle instructions once I get it to work.
I also ran into this today - the fix was adding the additional repo source @BenjaminHolland suggested in the original post. Found in version 4.3.3, the latest at the time of this post.