Details
-
Type:
Sub-task
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
C:\dev\grailsapp>mvn clean
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - com.hyt:grailsapp:war:1.0-SNAPSHOT
[INFO] task-segment: [clean]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[WARNING] Attempting to build MavenProject instance for Artifact (org.grails:grails-maven-plugin:0.4-20081111.072928-5) of type: m
aven-plugin; constructing POM artifact instead.
[INFO] [grails:maven-clean {execution: default}]
[INFO] Running pre-compiled script
Environment set to development
Warning, target causing name overwriting of name default
log4j:WARN No appenders could be found for logger (org.springframework.core.io.support.PathMatchingResourcePatternResolver).
log4j:WARN Please initialize the log4j system properly.
[INFO] Unable to load script 'Clean' (error: C:\dev\grailsapp\target\grails-lib not found.)
[INFO] Run 'grails help' for a complete list of available scripts.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Grails returned non-zero value.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16 seconds
[INFO] Finished at: Thu Nov 13 12:38:44 EST 2008
[INFO] Final Memory: 17M/127M
[INFO] ------------------------------------------------------------------------
This same error happens when one uses the grails-maven-archetype to create a grails project, then CDs into that project and runs 'mvn grails:create-app'. The latter generates yet another grails project within the first one. After that, all mvn commands cause this error to occur.