Anywho, the comment I recieved informed me that Grails 1.1 Maven support is out, giving Maven developers much needing air-mileage towards a Grails firstclass-citizen-goldcard. Predecessor Octo was, what I reckon, a shell around Ant scripts for doing Grails tasks, distancing Maven from responsibility of doing the nitty-gritty building and wiring.
So why should you care who builds your Grails project?
Because of the nifty reusable plugin functionality you get out of the box from maven. And more importantly with Grails, control of how you wire your app together.
The current state of the new Maven plugin
I can't see no Ant anywhere. It might be because I've been lazy and havent poked around the poms, but until contradicted, I choose to believe that Maven is in charge. One difference is the added folders, src/main/webapp aso. Does it work as it should yet? Of course not, it wouldn't be bleeding edge if it did, but well enough for me to get a good impression and a list of issues to report back on.
If the Maven plugin picks up speed inside GrailsDev, I'm a happy camper! Good Work!
Post a Comment
Spam will be pruned