Open kvsankar opened 9 years ago
It appears that this issue is the same as or is related to https://github.com/grails/grails-maven/issues/54 . I was able to get the build working by enabling fork.
I, too, am still experiencing this issue. 2.4.3 works, but 2.4.4 and 2.4.6 have the issues you described.
My maven project has multiple modules. One of them is a Grails project which uses the grails-maven-plugin. I noticed a difference between versions 2.4.4 and 2.4.3.
2.4.4 behavior - When
mvn install
tries to build the WAR file, the assets pipeline plugin tries to pre-compile the assets. These are put into$PROJECTROOT/target/assets
instead of$PROJECTROOT/grailsModule/target/assets
. Here's the relevant snippet from the build output:The directory
target/assets
is created in/path/to/project
instead of/path/to/project/grailsmodule
.2.4.3 behavior - works fine.
I am using JDK 1.6, Grails 2.4.5, asset pipeline plugin version 1.9.9, and Maven 3.1.1. The behavior is the same for Windows and Linux builds.
Is there a work-around for this issue?