|
If you were logged in you would be able to see more operations.
|
|
|
I tested out http://www.grails.org/Maven+Integration today, and thought I'd share the issues others may face when testing out Grails/Maven.
- May have a problem running from Maven v2.0.6. "Ignoring available plugin update: 2.0-alpha-2 as it requires Maven version 2.0.7" Worked fine in 2.0.9
- \'s are exluded from the "JUST DO IT" archetype snippet
- No link to how to comment/report bug from webpage
- Would be preferrable with short instructions.txt file at root of project with for example "mvn grails:...."
- JTA dependency requires manual download process - could perhaps be exluded?
- Had problems with running with Maven on my mac - may propably be relation to pollution of maven config / repo
- Problem running grails commands after "mvn clean" - target/grails-lib not found. mvn package solves problem
- Starting up jetty with "mvn grails:run-app" makes jetty answer, but http://localhost:8080/my-app returns 503. Starting the script is also peculiarly fast...
- When running mvn grails:run-app-https, I got the message that the folder ~/.grails/1.1-SNAPSHOT/ssl couldn't be created. Creating the folder manually solved the problem.
Great Work on the Maven plugin BTW!
http://stigl.wordpress.com/grails-11-got-maven-support-so-what?
|
|
Description
|
I tested out http://www.grails.org/Maven+Integration today, and thought I'd share the issues others may face when testing out Grails/Maven.
- May have a problem running from Maven v2.0.6. "Ignoring available plugin update: 2.0-alpha-2 as it requires Maven version 2.0.7" Worked fine in 2.0.9
- \'s are exluded from the "JUST DO IT" archetype snippet
- No link to how to comment/report bug from webpage
- Would be preferrable with short instructions.txt file at root of project with for example "mvn grails:...."
- JTA dependency requires manual download process - could perhaps be exluded?
- Had problems with running with Maven on my mac - may propably be relation to pollution of maven config / repo
- Problem running grails commands after "mvn clean" - target/grails-lib not found. mvn package solves problem
- Starting up jetty with "mvn grails:run-app" makes jetty answer, but http://localhost:8080/my-app returns 503. Starting the script is also peculiarly fast...
- When running mvn grails:run-app-https, I got the message that the folder ~/.grails/1.1-SNAPSHOT/ssl couldn't be created. Creating the folder manually solved the problem.
Great Work on the Maven plugin BTW!
http://stigl.wordpress.com/grails-11-got-maven-support-so-what? |
Show » |
Sort Order:
|
Sub-task
Resolved
Trivial
2. I'll work out a way of including them. The Wiki engine doesn't like them much.
3. Good point - I'll add one.
4. Okey-dokey
5. If you want GORM/Hibernate, I believe you need the JTA dependency.
6. Graeme seemed to have problems on his Mac - maybe there is an odd platform issue here
7. gngng! I thought I'd fixed that. I'll have to look again.
8. It's a bug
9. Ditto
In answer to your blog post, Maven isn't quite in control since the various phases execute the corresponding Gant scripts. So there is quite a bit of duplication. For example, in the "compile" phase the Maven compile plugin goes first, and then the Grails plugin executes the corresponding "Compile" Gant script. Since plugins can hook into the Grails build system and influence it (for example by adding to the compiler classpath), bypassing it means some things won't work. I'm interested to see just how well the current approach works and whether we need to change tack.
Thanks for the feedback Stig.
1. The original plugin had a requirement of 2.0.7, so I haven't changed it. Is 2.0.6 a widely used version? If so, it may be worth downgrading the restriction to 2.0.4 say. I don't know what changed between the various patch releases
2. I'll work out a way of including them. The Wiki engine doesn't like them much.
3. Good point - I'll add one.
4. Okey-dokey
5. If you want GORM/Hibernate, I believe you need the JTA dependency.
6. Graeme seemed to have problems on his Mac - maybe there is an odd platform issue here
7. gngng! I thought I'd fixed that. I'll have to look again.
8. It's a bug
9. Ditto
In answer to your blog post, Maven isn't quite in control since the various phases execute the corresponding Gant scripts. So there is quite a bit of duplication. For example, in the "compile" phase the Maven compile plugin goes first, and then the Grails plugin executes the corresponding "Compile" Gant script. Since plugins can hook into the Grails build system and influence it (for example by adding to the compiler classpath), bypassing it means some things won't work. I'm interested to see just how well the current approach works and whether we need to change tack.