On a team doing a java project (not the one for work. I hate that one and wish I could find a new job, it sucked that much joy out of life) got the java.lang.UnsatisfiedLinkError: no lwjgl in java.library.path error when I tried to run a reference project I was reviewing.
The two answers that I liked the most (because I could have just imported the lwjgl jar, but then the project would have that reference to the path on my Mac, and the source I downloaded had the authors Windows path, so it’s all stupid at this point) were to use a plugin to extend the M2E Maven plugin for Eclipse — see http://maven.40175.n5.nabble.com/How-to-manage-librairy-with-native-dll-in-maven-td5652069.html … basically add the http://mavennatives.googlecode.com/svn/eclipse-update/ location when adding software to eclipse and then add the plugin…
then add the following to your pom.xml:
<plugin> <groupId>com.googlecode.mavennatives</groupId> <artifactId>maven-nativedependencies-plugin</artifactId> <version>0.0.6</version> <executions> <execution> <id>unpacknatives</id> <phase>generate-resources</phase> <goals> <goal>copy</goal> </goals> </execution> </executions> </plugin>
— and then add
to the VM arguments in your run configuration — https://groups.google.com/forum/?fromgroups=#!topic/playn/E2t7gNh4ab0 is where I got that one.
And it was all good. The reference project in questions sucked, but at least I was able to get Maven to do what I think it should do…