In order to develop grails projects for the enterprise, netbeans should provide support for maven & grails together so
that the developer can add dependencies to a maven pom.xml file and the netbeans grails project will recognize those
dependencies and build the grails project using the maven lifecycle instead of grails.
reassigning to grails, that's where the changes need to be added
I am quite new here but is there any progress? Has anyone started working on this issue?
Thanks for the update
Is there a plan for fixing this issue?
It seems to be at least somewhat better in Netbeans 7.0. In a Maven Java project with both Java/Groovy sources, when editing Groovy files the class import auto-complete throws: "unable to resolve class". Although I'm able to enter the required imports manually without problems.
Without auto-import, groovy support is quite crippled though.
This is really needed. IDE Does not recognize deps in the pom.xml. This prevents me from using the IDE for grails dev. :( Commands need to execute mvn grails:* commands as well.
I know this is an old issue that seems to have very little priority for the product, but I wanted to add my vote and comments.
Could we at least have the ability to open a project that is both Grails and Maven as a Maven project? Currently, you can only open it as Grails. This causes problems because the project can't find dependencies and other maven projects that depend on the grails project don't find those dependencies and thus report errors.
Also, this actually prevents our corporation from being able to use Netbeans. It seems the only IDE that properly deals with this is the commercial version of Intellij IDEA which is quite pricey. I'd love to be able to use Netbeans for this, and it would allow us to share our code to other teams that don't have licenses for Intellij IDEA.
Anyway, I'd love to see this reconsidered for an upcoming version.