Posted by io7m on Jul 12, 2013; 12:13pm
URL: https://forum.jogamp.org/Atomic-jars-in-Maven-Central-Gradle-build-system-tp4029555p4029582.html

'Lo.

The way Maven downloads artifacts means that the native libraries for a given package will
be stored in the same directory as the primary jar file for that package. Unfortunately, Gradle
seems to break that assumption. We've had a brief talk about it and it seems like the best way
to deal with this would be to provide some sort of plugin mechanism for the name resolution,
so that GlueGen knows how to find native libraries in Gradle caches.

As Sven will emphasize: It's important to remember that looking up a file entails a network lookup
on some systems, so we really can't use any system that involves trying all sorts of different filenames
until one of them works.

Patches/ideas welcome!