Grails Maven Plugin

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: None
• Fix Version/s: None
• Component/s: None
• Labels:

  None

If you have quartz as a dependency in your project it might happen that you are unable start grails with "mvn grails:run-app" getting:

Application expects grails version [1.1.1], but GRAILS_HOME is version [null]

The problem is that BuildSettings.groovy loads properties from the build.properties file in the grails-bootstrap artifact.
However, a property file with the same name is also located in the quartz artifact. Depending on your luck the class loader will look into the correct artifact first - but maybe not. Its completely random because a Set is used for the artifacts.

This problem was also mentioned here:
http://javagrailsetc.blogspot.com/2009/04/problem-solved-application-expects.html

The best way to fix this seem to be to renamed the property file to something like "grails.build.properties".

Alternatively, the maven plugin should ensure that the grails-bootstrap artifact comes first in the classpath.
I used this approach for my workaround. I added in AbstractGrailsMojo#runGrails:

// make sure grails-bootstrap comes first
Artifact[] sortedDeps = new Artifact[deps.size()];
int i = 1;
for (Iterator iter = deps.iterator(); iter.hasNext();) {
    Artifact artifact = (Artifact) iter.next();
    if ("org.grails".equals(artifact.getGroupId()) && "grails-bootstrap".equals(artifact.getArtifactId())) {
        sortedDeps[0] = artifact;
    } else {
        sortedDeps[i] = artifact;
        i++;
    }
}

And changed

for (Iterator iter = deps.iterator(); iter.hasNext();) {

to

for (Iterator iter = Arrays.asList(sortedDeps).iterator(); iter.hasNext();) {

Regards,
Markus

1. 

   AbstractGrailsMojo.java.patch

   11/Jan/10 3:52 AM

   1 kB

   Martin Gerlach

• Assignee:

  Unassigned

  Reporter:

  Markus Kramer

• Created:

  12/Aug/09 9:45 AM

  Updated:

  30/Mar/11 4:12 AM

  Resolved:

  24/Sep/10 9:38 AM