This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Import of Grails project v1.1.1 failed to import correctly. 1. The ~/build.xml file that Grails creates was overwritten by the NetBeans build.xml file. 2. Best I can tell, it didn't recognize the project as being a Grails project. i.e. run said it couldn't find a main class. Loving the groovy support, thanks team.
I doubt you should be using the Eclipse importer for a Grails project to begin with. My understanding was that you can simply File > Open Project and open a Grails app directly, ignoring any Eclipse metadata. If true, then the bug is that the Eclipse importer even allows you to click Next - it should tell you to stop and just open the project directly. phejl would you like to comment? (The Eclipse importer only handles Java SE and Java EE WAR projects, for which there is no generally accepted IDE-independent source metadata format. Rails and Grails define the source project layout so NB can open it directly; any Eclipse metadata is derivative, a workaround for the fact that Eclipse cannot yet open special project types natively. Same with Maven - if there's a pom.xml, NB can open it without further ado, and any .project/.classpath should be ignored.)
I was able to just open the project's folder and NetBeans v6.7 recognized the project as a Grails/Groovy project. I'm changing this from a bug to an enhancement request. Eclipse user's are familiar with importing projects, plus Netbeans already shows the import of an eclipse project, what I'd like to have added is the import of a Grails project. The functionality of the import would be the same as opening a Grails project.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss