Grails 1.2 M4 and Maven
|
View:
New views
11 Messages
—
Rating Filter:
Alert me
|
 |
Grails 1.2 M4 and Maven
by Graeme Rocher-3
::
Rate this Message:
Hi all,
If you are a Maven user, I have published the Grails 1.2 M4 binaries to Maven. I have also deployed a new 1.2-SNAPSHOT of the Maven plugin and archetype that works with 1.2 M4. Please try these out by typing: mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate \ -DarchetypeGroupId=org.grails \ -DarchetypeArtifactId=grails-maven-archetype \ -DarchetypeVersion=1.2-SNAPSHOT \ -DgroupId=example -DartifactId=my-app And report any issues. Note you will need the following in your ~/.m2/settings.xml: <settings> <pluginGroups> <pluginGroup>org.grails</pluginGroup> </pluginGroups> </settings> Thanks -- Graeme Rocher Head of Grails Development SpringSource - A Division of VMware http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Grails 1.2 M4 and Maven
by Peter Niederwieser
::
Rate this Message:
The show stoppers I had with M3 are solved, but I'm still struggling:
1. package-plugin goal fails with: [INFO] [grails:package-plugin {execution: package-plugin}] [INFO] Using Grails 1.2-M4 Running pre-compiled script Warning, target causing name overwriting of name compile Warning, target causing name overwriting of name compilePlugins Warning, target causing name overwriting of name compilepackage Warning, target causing name overwriting of name compilegsp [delete] Deleting directory /swd/prj/spock/trunk/spock-grails/target/plugin-info [mkdir] Created dir: /swd/prj/spock/trunk/spock-grails/target/plugin-info [copy] Copying 1 file to /swd/prj/spock/trunk/spock-grails/target/plugin-info [delete] Deleting: /swd/prj/spock/trunk/spock-grails/grails-spock-0.3-SNAPSHOT.zip [zip] Building zip: /swd/prj/spock/trunk/spock-grails/grails-spock-0.3-SNAPSHOT.zip [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Unable to copy the plugin ZIP to the target directory [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to copy the plugin ZIP to the target directory at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to copy the plugin ZIP to the target directory at org.grails.maven.plugin.GrailsPackagePluginMojo.execute(GrailsPackagePluginMojo.java:68) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more As a workaround, I use the exec goal with command "package-plugin". 2. -DskipTests is not honored. Fortunately this is not a show stopper. 3. There is no release-plugin goal. Therefore I try to use the exec goal with command "release-plugin" and args "--zipOnly", but run into the following problems: 3a. org.tmatesoft.svn.core.SVNException: svn: Source and dest appear not to be in the same repository (src: 'https://spock.googlecode.com/svn/trunk/spock-grails'; dst: 'https://svn.codehaus.org/grails-plugins/grails-spock/tags/RELEASE_0_3-SNAPSHOT') I get the same error w/o Maven (grails release-plugin --zipOnly); other people had the same problem, but I can't find how to solve this (esp. since I'm doing a zip-only release). 3b: Grails asks for SVN username, password, and commit message; don't know how I can let the CI build provide this information (esp. commit message). Cheers, Peter
|
|
|
Re: Grails 1.2 M4 and Maven
by Luke Daley
::
Rate this Message:
On 07/11/2009, at 2:10 PM, Peter Niederwieser wrote: > 3a. org.tmatesoft.svn.core.SVNException: svn: Source and dest appear > not to > be in the same repository (src: > 'https://spock.googlecode.com/svn/trunk/spock-grails'; dst: > 'https://svn.codehaus.org/grails-plugins/grails-spock/tags/ > RELEASE_0_3-SNAPSHOT') > > I get the same error w/o Maven (grails release-plugin --zipOnly); > other > people had the same problem, but I can't find how to solve this > (esp. since > I'm doing a zip-only release). Please see http://jira.codehaus.org/browse/GRAILS-5319 for a potential fix. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Grails 1.2 M4 and Maven
by Luke Daley
::
Rate this Message:
On 07/11/2009, at 2:10 PM, Peter Niederwieser wrote: > 3b: Grails asks for SVN username, password, and commit message; > don't know > how I can let the CI build provide this information (esp. commit > message). Please see http://jira.codehaus.org/browse/GRAILS-5320 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Grails 1.2 M4 and Maven
by Helmut Denk
::
Rate this Message:
daimonion - the inner voice says:
grails should give up to support maven that way. put only half of the investment that was dumped into maven-support into gradle-builds and you get consistent, sustainable builds of a high quality for grails. resolving and publishing to maven-archives is supported by gradle out of the box ... so you get the basic maven-support without even having to cope with maven. [i guess, that maven-support exists to attract poeple to grails, but even more people will be attracted the other way round.] gruesse |
|
|
Re: Grails 1.2 M4 and Maven
by Luke Daley
::
Rate this Message:
On 07/11/2009, at 5:07 PM, Helmut Denk wrote: > daimonion - the inner voice says: > > grails should have never started to support maven that > way. put only half of the investment that was dumped into > maven-support into gradle-builds and you get consistent, > sustainable builds of a high quality for grails. > > resolving and publishing to maven-archives is supported by > gradle out of the box ... so you get the basic maven-support > without even having to cope with maven. I can't find any info on using Gradle to build Grails projects. Link? --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Grails 1.2 M4 and Maven
by Luke Daley
::
Rate this Message:
On 07/11/2009, at 5:07 PM, Helmut Denk wrote: > daimonion - the inner voice says: > > grails should have never started to support maven that > way. put only half of the investment that was dumped into > maven-support into gradle-builds and you get consistent, > sustainable builds of a high quality for grails. > > resolving and publishing to maven-archives is supported by > gradle out of the box ... so you get the basic maven-support > without even having to cope with maven. I can't find any info on using Gradle to build Grails projects. Link? --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Grails 1.2 M4 and Maven
by Helmut Denk
::
Rate this Message:
hello luke,
i corrected my statement a little bit from: >>grails should have never started to support maven that way to : >>grails should give up to support maven that way. >> ... >>i guess, that maven-support exists to attract poeple to >>grails, but even more people will be attracted the other >>way round. i dont think, that a gradle-build for grails-apps exists. but there is one for the gails-system. i think hans dockter is about to do some refactorings on it ... all in all this is probably something for the 2.x roadmap ... the recently implemented dsl for dependency-management seems like a step into that direction. one of the interresting questions, that will come up with those things is: where to draw the borderline between dependency-management for the build and dependency-management for the runtime. the diffenence is not so clear because of the dynamic nature of groovy. have a successful week
|
|
|
Re: Grails 1.2 M4 and Maven
by Peter Ledbrook
::
Rate this Message:
>>>grails should give up to support maven that way.
>>> ... >>>i guess, that maven-support exists to attract poeple to >>>grails, but even more people will be attracted the other >>>way round. > > i dont think, that a gradle-build for grails-apps exists. > but there is one for the gails-system. There isn't as far as I'm aware. Note that the amount of effort that went into explicit Maven support was minor compared to the work on making Grails integrate with *all* build systems (Ant, Maven, Gradle, etc.). Most of the Maven-specific stuff was already there from the Octo plugin, so all I needed to do was update it for the internal Grails changes. Cheers, Peter --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Grails 1.2 M4 and Maven
by Graeme Rocher-3
::
Rate this Message:
On Mon, Nov 9, 2009 at 9:52 AM, Peter Ledbrook <peter@...> wrote:
>>>>grails should give up to support maven that way. >>>> ... >>>>i guess, that maven-support exists to attract poeple to >>>>grails, but even more people will be attracted the other >>>>way round. >> >> i dont think, that a gradle-build for grails-apps exists. >> but there is one for the gails-system. > > There isn't as far as I'm aware. > > Note that the amount of effort that went into explicit Maven support > was minor compared to the work on making Grails integrate with *all* > build systems (Ant, Maven, Gradle, etc.). Most of the Maven-specific > stuff was already there from the Octo plugin, so all I needed to do > was update it for the internal Grails changes. Additionally, like it or not (and I don't ;-), Maven has a clear presence in many companies whilst Gradle does not yet. I hope it does one day achieve the level of adoption Maven has, I truly do. Cheers > > Cheers, > > Peter > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Graeme Rocher Head of Grails Development SpringSource - A Division of VMware http://www.springsource.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Grails 1.2 M4 and Maven
by pratik patel-6
::
Rate this Message:
This is how I had to run generator (notice the last arg): mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate -DarchetypeGroupId=org.grails -DarchetypeArtifactId=grails-maven-archetype -DarchetypeVersion=1.2-SNAPSHOT -DgroupId=example -DartifactId=my-app -DarchetypeRepository=http://snapshots.repository.codehaus.org/
This seemed to run OK, however running a mvn install produced this: <snip> [copy] Warning: /Users/prpatel/dev/tmp/my-app/plugins/hibernate-1.2-M4/src/java not found.
[jar] Building jar: /Users/prpatel/dev/tmp/my-app/target/my-app-1.0-SNAPSHOT.war [delete] Deleting directory /Users/prpatel/dev/tmp/my-app/target/stage Done creating WAR /Users/prpatel/dev/tmp/my-app/target/my-app-1.0-SNAPSHOT.war
[INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Unable to copy the WAR file to the target directory
Pasted below is my settings.xml, which I had to hack a bit to get it this far. Graeme, can you post your settings.xml, I suspect you may have something either there on the in the MAVEN_OPTS that we're missing.
<settings> <pluginGroups> <pluginGroup>org.grails</pluginGroup> </pluginGroups> <profiles>
<profile> <id>grails</id> <pluginRepositories> <pluginRepository> <id>Codehaus</id>
<url>http://repository.codehaus.org</url> <snapshots> <enabled>true</enabled>
</snapshots> <releases> <enabled>true</enabled> </releases> </pluginRepository>
<pluginRepository> <id>Codehaus Snapshots</id> <url>http://snapshots.repository.codehaus.org/</url>
<snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>false</enabled>
</releases> </pluginRepository> <pluginRepository> <id>SourceForge</id>
<releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled>
</snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles>
<activeProfile>grails</activeProfile> </activeProfiles> </settings> cheer -p |
| Free embeddable forum powered by Nabble | Forum Help |
