Details
-
Type:
Sub-task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Environment:Windows XP Professional; Encountered this problem with Grails 1.3.2 and 1.2.2, using Groovy 1.7.3
Description
Following the instructions on Grails Maven Integration, I created a new project using the maven archetype.
The archetype completes successfully and after I execute mvn initialize my directory structure has a familiar Grails feel to it along with a pom.xml file. Initially, I encountered dependency errors I was able to work through with the 1.2.2 version of the plugin/grails/archetype that I did not encounter when I tried with the 1.3.2 version. Eventually, I had both builds failing with the same message:
[INFO] ----------------------------------------------------- [ERROR] BUILD ERROR [INFO] ----------------------------------------------------- [INFO] Unable to start Grails Embedded error: java.lang.reflect.InvocationTargetException conversion failed
When I use the grails command directly:
grails run-app
I did not encounter this problem, even though the same task was apparently executed here as well:
[native2ascii] Converting 13 files from C:\grails-projects\charfox-app\grails-ap p\i18n to C:\Documents and Settings\clatimer\.grails\1.3.2\projects\charfox-app\ resources\grails-app\i18n
The output right before the build failed was:
[native2ascii] Converting 12 files from C:\grails-projects\charfox-app\grails-ap p\i18n to C:\grails-projects\charfox-app\target\resources\grails-app\i18n
After some additional digging and reading through some work a coworker had done, I was able to work around this problem by modifying my grails-app\conf\Config.groovy file and setting grails.enable.native2ascii to false.
// enabled native2ascii conversion of i18n properties files // grails.enable.native2ascii = true -> *this was the problem* grails.enable.native2ascii = false
I did not encounter this problem when I used the grails run-app command directly, even though the output indicated that it made the same [native2ascii] call.
After further investigation, this (and a ton of other problems I have been encountering) seem to stem from the fact that I was using a custom maven installation that used the IBM JDK instead of the Sun JDK. By adding the JVM argument -Xverify:none I solved nearly all the issues I have been encountering with Grails+Maven.