Comment #2 by jacobvoneyben:
The problem is that you cannot define what java the flexcompiler will
run under.
Trying to run the compiler having java 1.4 in my path resulted in a
nullpointer as well.
The flex mojo has to be run
Inspired by how the maven-surefire-plugin set a different jvm I would
like to
contribute with code changing the hardcoded "java" executable to a
property or
java.home if not set.
That did the trick for us using
Attachments:
0 bytes
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Comment #3 by jacobvoneyben:
The problem is that you cannot define what java the flexcompiler will
run under.
Trying to run the compiler having java 1.4 in my path resulted in a
nullpointer as well.
The flex mojo has to be run
Inspired by how the maven-surefire-plugin set a different jvm I would
like to
contribute with code changing the hardcoded "java" executable to a
property or
java.home if not set.
That did the trick for us having java 1.4 in the path for the running user
Attachments:
AbstractFlexMojo.java 13.2 KB
Comment #4 by jacobvoneyben:
I wrapped the above changes in a svn patch
Attachments:
fixed_jvm_issue.patch 10.1 KB