On Thu, 21 Jun 2012 15:39:58 +0000 <[email protected]> wrote:
> On Thu, 21 Jun 2012 17:27:18 +0200 > Anders Hammar <[email protected]> wrote: > > > Yes, you use classifiers for that. Normally not a clean Maven > > solution though. Please do understand they will all have the same > > set of dependencies as they share one pom. > > Yes, the dependencies are fine. I'm aware this isn't a very clean > solution, but it's by far the least intrusive so far. I'd normally > not do anything like this, but the library in question has a rather > complicated relationship with native libraries and makes some > assumptions that don't necessarily apply when working with Maven. > > Anyway, I'll look into classifiers, thanks. OK, I think I'm very close to a solution now. Please see: http://mvn.io7m.com/org/jogamp/jogl/jogl.all/2.0-rc9/ Note that all of the auxiliary jars are deployed in the same location as the main jar, meaning the library can find the jar files it needs in order to unpack. Unfortunately, I'm now running up against the problem that it's rather labour intensive to fetch all of the native jars (and we do want to fetch *ALL* of them for deployment). A user wanting to use the library has to say: <dependency> <groupId>org.jogamp.jogl</groupId> <artifactId>jogl.all</artifactId> <version>2.0-rc9</version> </dependency> <dependency> <groupId>org.jogamp.jogl</groupId> <artifactId>jogl.all</artifactId> <version>2.0-rc9</version> <classifier>natives-linux-amd64</classifier> </dependency> <dependency> <groupId>org.jogamp.jogl</groupId> <artifactId>jogl.all</artifactId> <version>2.0-rc9</version> <classifier>natives-linux-i586</classifier> </dependency> ... I sort of want to have the project depend on its own extra, classified artifacts, but I imagine that's considered a circular dependency and will drive some tools insane... --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
