KrazyTheFox wrote:Chris H. wrote:I tried to launch the most recent windows-linux snapshot build via the "forge.command" shell script and forge did not launch. Looks like the script that creates the "forge.command" shell script is not naming the jar file correctly.
That's odd. Running "mvn -U -B clean -P windows-linux install" uses the correct names for the files over here. Here's what I got:
http://www.krazyweb.net/forge/forge-gui-desktop-1.5.16-SNAPSHOT.zipIs it just "forge.command" that has the incorrect file name?
Hmmm, not quite sure what is now causing this latest problem. I can launch the widows-linux 1.5.15 beta via it's included forge.command file without problems.
If I try to use the command file from todays snapshot build forge fails to launch and I get the error instead. Taking a closer look I guess that the "cd" line is causing the failure. I think that the command file is stopping before it gets to launch the forge jar file. So it looks like the command file is using the correct name for the jar and the problem is in the "cd" line.
I downloaded your archive and then attempted to launch forge via the command file after I extracted the archive. I get the same error report in my terminal window.
- Code: Select all
Last login: Mon Apr 21 19:25:33 on ttys000
CardForge:~ me$ /Users/me/Desktop/forge-gui-desktop-1.5.16-SNAPSHOT/forge.command ; exit;
-bash: /Users/me/Desktop/forge-gui-desktop-1.5.16-SNAPSHOT/forge.command: /bin/sh^M: bad interpreter: No such file or directory
logout
[Process completed]
