-
Notifications
You must be signed in to change notification settings - Fork 61
Can Xebium run Java Scripts compiled in 1.7 (OS X)? #110
Comments
I'm not entirely sure what you mean by "Java Scripts", but I presume you mean SLIM fixtures. If so, this is a problem with the way you're using FitNesse, not really related to Xebium. FitNesse will load any jars that are supported by the JVM you're using to start the SLIM service. I expect you have a a Java 6 JVM on the PATH. Can you put your Java 7 JVM on the PATH? Does that help? Kind regards, Arnout |
Thanks Arnout, |
I'm not familiar with OS X myself, but I presume you could open a terminal and run 'java -version'. |
Ah, yes I did try that sometime ago on Terminal. I currently have 1.7.0_45. Having said that I still got the Exception error till I recompiled my Java Project to 1.6 |
How are you starting FitNesse? After running a test, what does the errorlog (under 'Captured output' or 'Errors occurred') show, in particular the start of the 'command' section? |
Apologize for the delay. I am starting it with the "mvn -Pfitnesse test" command in terminal. T E S T SRunning com.xebia.fitnesse.selenium.JavascriptTestCase Results : Tests run: 86, Failures: 0, Errors: 0, Skipped: 7 [INFO] main: ----------The error message that occurs when ran is: -----Again, once the project and associated jar files are downgraded to 1.6 everything works fine. Hence my question ;) |
What does the errorlog (under 'Captured output') show, in particular the start of the 'command' section? I'd expect that to start with 'java -cp', but let's validate that before making assumptions. |
Hello,
I've had exception errors in Xebium (via Fitnesse) when trying to run Java Scripts compiled in 1.7 (OS X). However after recompiling the project and appropriate jar files to 1.6 Xebium is able to run the Java Scripts fine. Is there a reason for this? If so, why and is there any ETA on when Xebium will be upgraded? If Xebium is able to run scripts in 1.7 let me know what I need to change to make this happen.
Thanks.
The text was updated successfully, but these errors were encountered: