Grails

run-war on new empty plgin project wont build - missing grails-app directory in builder code

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 2.0.3
  • Fix Version/s: None
  • Component/s: Plugins
  • Labels:
  • Environment:
    STS 2.9.1 on windows 7 32 bit

Description

create a new 'empty' plugin project

at the commang prompt type run-war <yourPlugin>

build fails like this

Base Directory: C:\Users\802518659\Documents\grails-workspace\tempPlugin

Loading Grails 2.0.3
Configuring classpath.
Environment set to development.....
Packaging Grails application....
Compiling 2 source files
[groovyc] Compiling 2 source files to C:\Users\802518659\.grails\2.0.3\projects\tempPlugin\plugin-classes
Compiling 2 source files.....
[copy] Copying 1 file to C:\Users\802518659\Documents\grails-workspace\tempPlugin\target\classes
Compiling 1 GSP file for package [tempPlugin]..
[mkdir] Created dir: C:\Users\802518659\.grails\2.0.3\projects\tempPlugin\stage
Compiling 1 GSP file for package [tempPlugin]...
Building WAR file
[copy] Copying 6 files to C:\Users\802518659\.grails\2.0.3\projects\tempPlugin\stage
[copy] Copied 7 empty directories to 4 empty directories under C:\Users\802518659\.grails\2.0.3\projects\tempPlugin\stage
Building WAR file.
[mkdir] Created dir: C:\Users\802518659\.grails\2.0.3\projects\tempPlugin\stage\plugins\temp-plugin-0.1
Building WAR file..
[copy] Copied 3 empty directories to 3 empty directories under C:\Users\802518659\.grails\2.0.3\projects\tempPlugin\stage\plugins\temp-plugin-0.1
Building WAR file....
[delete] Deleting directory C:\Users\802518659\.grails\2.0.3\projects\tempPlugin\stage
Building WAR file.....
Error Error executing script RunWar: : C:\Users\802518659\.grails\2.0.3\projects\tempPlugin\resources\grails-app does not exist.
: C:\Users\802518659\.grails\2.0.3\projects\tempPlugin\resources\grails-app does not exist.
at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:483)
at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:475)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at groovy.util.AntBuilder.performTask(AntBuilder.java:260)
at groovy.util.AntBuilder.nodeCompleted(AntBuilder.java:220)
at groovy.util.BuilderSupport.doInvokeMethod(BuilderSupport.java:147)
at groovy.util.AntBuilder.doInvokeMethod(AntBuilder.java:170)
at groovy.util.BuilderSupport.invokeMethod(BuilderSupport.java:64)
at org.codehaus.gant.GantBuilder.invokeMethod(GantBuilder.java:99)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
at RunWar$_run_closure4.doCall(RunWar:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1047)
at groovy.lang.ExpandoMetaClass.invokeMethod(ExpandoMetaClass.java:1110)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:877)
at groovy.lang.DelegatingMetaClass.invokeMethod(DelegatingMetaClass.java:149)

the work around is to have to go into your .grails\2.0.3\projects\tempPlugin\resources directory (note this is not in your eclipse workspace)

then manually create an empty grails-app direcory

re run the run-war command it it works now

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Will Woodman added a comment -

apologies

cant see where to adjust the priority on the input form

its really a minor /medium and theres an manual work around

Show
Will Woodman added a comment - apologies cant see where to adjust the priority on the input form its really a minor /medium and theres an manual work around
Will Woodman made changes -
Field Original Value New Value
Status Open [ 1 ] Edit [ 10000 ]
Graeme Rocher made changes -
Priority Major [ 3 ] Minor [ 4 ]
Hide
Permalink
John Holme added a comment - - edited

I have a similar problem running "mvn clean install" against a grails plugin project using grails 2.0.3 and maven 2.2.1. However, the suggested workaround does not fix it. What I'm actually trying to do here is install this grails plugin in the local maven repo. I'm not sure this is the right command to use, but "grails maven-install" is broken in this grails-maven project, so I thought the mvn install command might do the trick.

Plugin packaged grails-env-auth-three-1.0-SNAPSHOT.zip
[INFO]
Moved plugin ZIP to 'C:\branches\envAuthThree\target\grails-env-auth-three-1.0-SNAPSHOT.zip'.
[INFO]
[grails:maven-war {execution: default}]
...
Running pre-compiled script
..................................
Packaging Grails application
........
Compiling 1 GSP file for package [envAuthThree]
...
Building WAR file
.....[INFO]
------------------------------------------------------------------------
[ERROR]
BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO]
Unable to start Grails

Embedded error: java.lang.reflect.InvocationTargetException
C:\branches\envAuthThree\target\resources\grails-app does not exist.
[INFO]
...
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to start Grails
...
Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
...
Caused by: java.lang.reflect.InvocationTargetException
...
Caused by: : C:\branches\envAuthThree\target\resources\grails-app does not exist.

additional stacktrace details are available if required.

Show
John Holme added a comment - - edited I have a similar problem running "mvn clean install" against a grails plugin project using grails 2.0.3 and maven 2.2.1. However, the suggested workaround does not fix it. What I'm actually trying to do here is install this grails plugin in the local maven repo. I'm not sure this is the right command to use, but "grails maven-install" is broken in this grails-maven project, so I thought the mvn install command might do the trick. Plugin packaged grails-env-auth-three-1.0-SNAPSHOT.zip [INFO] Moved plugin ZIP to 'C:\branches\envAuthThree\target\grails-env-auth-three-1.0-SNAPSHOT.zip'. [INFO] [grails:maven-war {execution: default}] ... Running pre-compiled script .................................. Packaging Grails application ........ Compiling 1 GSP file for package [envAuthThree] ... Building WAR file ..... [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Unable to start Grails Embedded error: java.lang.reflect.InvocationTargetException C:\branches\envAuthThree\target\resources\grails-app does not exist. [INFO] ... Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to start Grails ... Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException ... Caused by: java.lang.reflect.InvocationTargetException ... Caused by: : C:\branches\envAuthThree\target\resources\grails-app does not exist. additional stacktrace details are available if required.
Hide
Permalink
John Holme added a comment - - edited

These are the steps I followed to create the plugin project that fails on "mvn install" per yesterday's post. One red flag is the artifactId of the plugin: when "envAuthThree" is specified as the artifactId on the archetype:generate command, 1) the plugin descriptor is generated incorrectly as "HThreeGrailsPlugin.groovy" (which I corrected) and 2) "mvn grails:validate-plugin" fails until the artifactId in the pom is changed from the auto-generated "envAuthThree" to "env-auth-three". Please let me know if there's a preferred series of steps to create a grails plugin project under maven.

1. create new grails-maven plugin project using maven's grails archetype
mvn archetype:generate -DarchetypeGroupId=org.grails -DarchetypeArtifactId=grails-maven-archetype -DarchetypeVersion=2.0.3 -DgroupId=com.iii -DartifactId=envAuthThree

  • in pom.xml
    • change packaging to "grails-plugin"
    • change maven-compiler-plugin from 1.5 to 1.6
    • change artifactId from envAuthThree to env-auth-three (otherwise mvn grails:validate-plugin fails)
  • run mvn initialize
    • plugin descriptor name is mangled by the initialize action
    • change name of plugin descriptor if required (s/b EnvAuthThreeGrailsPlugin.groovy)
  • modify EnvAuthThreeGrailsPlugin.groovy
    • customize for this project
    • omit spring-security-core dependsOn (add this in later)
  • ensure app name and version correspond:
    • pom.xml - change artifactId from envAuthThree to env-auth-three (per validate-plugin), 1.0-SNAPSHOT
    • application.properties - change envAuthThree to env-auth-three (per validate-plugin), 1.0-SNAPSHOT
    • EnvAuthThreeGrailsPlugin.groovy - 1.0-SNAPSHOT
  • modify BuildConfig.groovy
    • "pom true" (dependencies and plugins will be defined in pom.xml)
    • "useOrigin true" (don't cache dependencies during development)
    • no dependencies or plugins should be defined in BuildConfig

2. run maven-grails commands

  • mvn grails:init-plugin - success
  • mvn grails:validate-plugin - fails
    • The plugin name in the pom.xml [envAuthThree] is not the expected 'env-auth-three' or 'grails-env-auth-three'. Please correct the pom.xml or the plugin descriptor.
    • changing artifactId in pom.xml from envAuthThree to env-auth-three
    • run again - success
  • mvn grails:maven-clean - success
  • mvn grails:maven-compile - success
  • mvn grails:package-plugin - success
  • //grails maven-install - fails
  • // Script 'MavenInstall' not found
  • mvn install - fails
    • app.name [envAuthThree] in application.properties is different of the artifactId [env-auth-three] in the pom.xml
    • > change app.name in application.properties from envAuthThree to env-auth-three
    • mvn install - fails
      • FATAL ERROR - java.lang.OutOfMemoryError: PermGen space
      • > change $MAVEN_OPTS from -Xms512m -Xmx2048m to -Xms1024m -Xmx4096m
    • mvn install - fails
      • FATAL ERROR - org.codehaus.classworlds.NoSuchRealmException: plexus.core
      • > add to $MAVEN_OPTS -XX:MaxPermSize=1024m
    • mvn clean install - fails
      • BUILD ERROR - Unable to start Grails
      • Embedded error: java.lang.reflect.InvocationTargetException
      • PermGen space
      • > change $MAVEN_OPTS -XX:MaxPermSize=4096m
    • mvn clean install - fails
      • Unable to start Grails
      • Embedded error: java.lang.reflect.InvocationTargetException
      • C:\branches\envAuthThree\target\resources\grails-app does not exist.
      • see http://jira.grails.org/browse/GRAILS-9058
      • adding the grails-app dir at ~/.grails/2.0.3/projects/envAuthThree/resources does not fix this problem.

Once I am able to successfully install this empty plugin, I'll start adding dependencies, plugins and artifacts one at a time.

Show
John Holme added a comment - - edited These are the steps I followed to create the plugin project that fails on "mvn install" per yesterday's post. One red flag is the artifactId of the plugin: when "envAuthThree" is specified as the artifactId on the archetype:generate command, 1) the plugin descriptor is generated incorrectly as "HThreeGrailsPlugin.groovy" (which I corrected) and 2) "mvn grails:validate-plugin" fails until the artifactId in the pom is changed from the auto-generated "envAuthThree" to "env-auth-three". Please let me know if there's a preferred series of steps to create a grails plugin project under maven. 1. create new grails-maven plugin project using maven's grails archetype mvn archetype:generate -DarchetypeGroupId=org.grails -DarchetypeArtifactId=grails-maven-archetype -DarchetypeVersion=2.0.3 -DgroupId=com.iii -DartifactId=envAuthThree in pom.xml change packaging to "grails-plugin" change maven-compiler-plugin from 1.5 to 1.6 change artifactId from envAuthThree to env-auth-three (otherwise mvn grails:validate-plugin fails) run mvn initialize plugin descriptor name is mangled by the initialize action change name of plugin descriptor if required (s/b EnvAuthThreeGrailsPlugin.groovy) modify EnvAuthThreeGrailsPlugin.groovy customize for this project omit spring-security-core dependsOn (add this in later) ensure app name and version correspond: pom.xml - change artifactId from envAuthThree to env-auth-three (per validate-plugin), 1.0-SNAPSHOT application.properties - change envAuthThree to env-auth-three (per validate-plugin), 1.0-SNAPSHOT EnvAuthThreeGrailsPlugin.groovy - 1.0-SNAPSHOT modify BuildConfig.groovy "pom true" (dependencies and plugins will be defined in pom.xml) "useOrigin true" (don't cache dependencies during development) no dependencies or plugins should be defined in BuildConfig 2. run maven-grails commands mvn grails:init-plugin - success mvn grails:validate-plugin - fails The plugin name in the pom.xml [envAuthThree] is not the expected 'env-auth-three' or 'grails-env-auth-three'. Please correct the pom.xml or the plugin descriptor. changing artifactId in pom.xml from envAuthThree to env-auth-three run again - success mvn grails:maven-clean - success mvn grails:maven-compile - success mvn grails:package-plugin - success //grails maven-install - fails // Script 'MavenInstall' not found mvn install - fails app.name [envAuthThree] in application.properties is different of the artifactId [env-auth-three] in the pom.xml > change app.name in application.properties from envAuthThree to env-auth-three mvn install - fails FATAL ERROR - java.lang.OutOfMemoryError: PermGen space > change $MAVEN_OPTS from -Xms512m -Xmx2048m to -Xms1024m -Xmx4096m mvn install - fails FATAL ERROR - org.codehaus.classworlds.NoSuchRealmException: plexus.core > add to $MAVEN_OPTS -XX:MaxPermSize=1024m mvn clean install - fails BUILD ERROR - Unable to start Grails Embedded error: java.lang.reflect.InvocationTargetException PermGen space > change $MAVEN_OPTS -XX:MaxPermSize=4096m mvn clean install - fails Unable to start Grails Embedded error: java.lang.reflect.InvocationTargetException C:\branches\envAuthThree\target\resources\grails-app does not exist. see http://jira.grails.org/browse/GRAILS-9058 adding the grails-app dir at ~/.grails/2.0.3/projects/envAuthThree/resources does not fix this problem. Once I am able to successfully install this empty plugin, I'll start adding dependencies, plugins and artifacts one at a time.
Burt Beckwith made changes -
Status Edit [ 10000 ] Open [ 1 ]

People

  • Assignee:
    Unassigned
    Reporter:
    Will Woodman
Vote (2)
Watch (3)

Dates

  • Created:
    Updated: