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.
can't create package at same time as creating domain class this can be done from the command line when creating a new project , even in a different directory, still asks if i want to upgrade to same version of grails y/n and there is no way to respond, this was posted previously requires the removal of .grails or creating the project from the command line.
> can't create package at same time as creating domain class > this can be done from the command line This is duplicate of issue 158246. Should be fixed pretty soon. > when creating a new project , even in a different directory, > still asks if i want to upgrade to same version of grails y/n > and there is no way to respond, this was posted previously You mean issue 158959? This was fixed and I'm not able to reproduce it anymore. What is the exact version of Grails and NetBeans you use? Thanks for the report!
I create a domain class, say "book", then delete it then if I try to create another domain class with the same name as "book" the netbeans ide freezes , asking if I want to overwrite the unit test book created by the first domain class "book's" creation y/n. there is no why to respond to y/n since the ide is frozen
package com.grailsinaction class Tag { static constraints = { } } if I right clicked grailsinaction the class ended up in com I had to create this from the command prompt one previous classes I created from the ide after creating the initial package from the dos prompt it does not let me enter a path in wizard; one other ide has poor grails support, but , their wizard has first line for grails command , second line for package name and new class name request in dot notation(argument line) and third line lists all available commands, but their editor is like notepad, absolutely featureless netbeans 6.7 - grails 1.1 - vista
BTW you don't have to use command line. In NetBeans 6.7 you can use "Run Grails Command..." from project context menu. In daily builds you can even assign shortcut to this action.
Should be fixed now.