** Uncaught Exception! ** when running "mvn package" on OSX about opsu HOT 13 CLOSED

Did you build that with maven? And do the jar releases work for you?

from opsu.

"mvn install" triggers this, as does "mvn compile exec:exec"

"mvn install -Djar" works fine

On 3 June 2015 at 16:06, Peter Tissen [email protected] wrote:

Did you build that with maven? And do the jar releases work for you?

—
Reply to this email directly or view it on GitHub
#87 (comment).

Jason Che-han Yip
http://jchyip.blogspot.com
"The truth does not change according to our ability to stomach it."
(Flannery O'Connor)

from opsu.

Does the liblwjgl.dylib file exist?

from opsu.

well, mvn install will definitely give an error because it can't find the library file in Users/jyip/dev/opsu/./target/natives/liblwjgl.dylib since that folder is your opsu! project folder (those libs are kept in Users/.m2/repository). Maven expects to find the libraries in the target folder by default UNLESS if you inform Maven the library iirc.
the use of "mvn install -Djar" is do the following (correct me if i am wrong, since this is what i have observed over the time of reading the source code):

• Resource copy to project target folder
• Compile source code to `opsu--generated.jar
• Copy all dependencies .jar file to project target folder
• use JarSplicePlus (itdelatrisu modified JarSplice)to shade (include) every single dependencies .jar file into another .jar (afaik opsu-<version>-shaded.jar).
• generates opsu-<version>-runnable.jar from `opsu--shaded.jar

from opsu.

In that case, is there a documentation change required for README.md? As in, is there another step required before mvn compile exec:exec would be expected to work?

from opsu.

you do need to have all required libraries added to opsu! dependencies.
compile exec:exec does the same thing as install -Djar (except that it just compiles the source code and run directly in the target folder without packaging to .jar).
if you can do install -Djar goal, you should be able to do compile exec:exec goal

from opsu.

Add to readme information about maven.
Need to use maven3 to compile project.
On ubuntu 14.04 this is something like:

sudo apt-get purge maven maven2 maven3
sudo apt-add-repository ppa:andrei-pozolotin/maven3
sudo apt-get update
sudo apt-get install maven3
cd {project_dir}
mvn compile exec:exec

from opsu.

@jchyip: does the post above solve your problem?

from opsu.

No it does not. I'm already using Maven 3. Tried this on Windows and it works fine. I don't see target/natives/liblwjgl.dylib in either OSX or Windows. Are you saying that this is supposed to be from the Maven repo?

from opsu.

Oh, my bad, the file doesn't exist. Are you using Java 8? From this post, it seems like this only affects Java 8 in OSX. Not sure what to do...

from opsu.

Looks like the short-term solution is to rename
target/native/liblwjgl.jnilib to target/native/liblwjgl.dylib. Perhaps
just make a note of this for OSX / Java 8 users?

On 14 June 2015 at 11:05, Jeffrey Han [email protected] wrote:

Oh, my bad, the file doesn't exist. Are you using Java 8? From this post
MultiMC/Launcher#371, it seems like this only
affects Java 8 in OSX. Not sure what to do...

—
Reply to this email directly or view it on GitHub
#87 (comment).

Jason Che-han Yip
http://jchyip.blogspot.com
"The truth does not change according to our ability to stomach it."
(Flannery O'Connor)

from opsu.

Well, it's possible to rename things in Maven (link) but I don't know if it's worth the trouble...

from opsu.

Seems like this was fixed when I updated LWJGL from 2.9.1 to 2.9.3. This is included in the changelog for the 2.9.2 release:

2014-11-28  Ioannis Tsakpinis <[email protected]>

    * src/java/org/lwjgl/LWJGLUtil.java, src/java/org/lwjgl/Sys.java,
    src/java/org/lwjgl/util/applet/AppletLoader.java: Replace .jnilib
    with .dylib on OS X with JDK 6. Resolve #100

from opsu.