I think crowne makes some really good points in the previous post. Personally, I think Brian's approaching is too much like trying to turn Grails into Maven… That is just not going to work.

Grails is not Maven, never will be. The goal here should be "How can we support integrating Grails development into Maven workflows/ projects".

I don't think we _need_ to change the grails project structure at all. We need to make Maven work with Grails. And only really enough to drive the process. There is no real advantage to imposing the Maven structure on a grails project _unless_ through Maven limitations we can't get it to work with the Grails structure.

That said, if compromises can be made that don't negatively impact Grails then sure why not.

I guess my point is, let's not get carried away here. Let's identify real use cases and make sure we support them.

LD.