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.
A while ago there was some discussion on nbui about better organization and validation for new packages vs. new folders. It seems we arrived at a consensus - I am just filing this so the decision does not fall through the cracks. See http://www.netbeans.org/www-nbui/msg01262.html
I did not pay attention to the discussion on nbui, but this should be solved by new project implementation. The Java package should be handled completely differently, then is now. I am assigning this to project team and we will try to handle this for 3.3.
Target milestone -> 3.3
Shouldn't this bug belong to java/clazz module instead of projects ?
I don't care which module addresses this - Yarda assigned it to projects.
As the link to the archive is broken ("thanks" to the upgrade of the website), could someone following the nbui@ discussion attach here the message actual message ?
Here it is: http://www.netbeans.org/servlets/ReadMsg?msgId=83211&listName=nbui http://www.netbeans.org/servlets/ReadMsg?msgId=83214&listName=nbui
Currently 'Add Folder' action in context menu allows you to create folder with arbitrary name. Now it's upon the java module to add 'Create Java Package' template.
Does Add Folder validate? If it is meant to be any folder, it shouldn't....
It looks for slashes (\, /) and prevents you to put them in forlder's name, but it still recognizes dots in the name and creates tree of folders according to parts separated by dots. Shouldn't I change this and look for slashes instead? Java template can then handle dots.
Perhaps yes. BTW that means that Java module needs to provide "package" template for 3.3, right ?
Yes, I think so.
Template implemetned for 3.3. Should we keep this as a RFE for new projects ?
I'm happy with the new template and I suspect projects will require lots of ui support. Shouldn't we close this issue and record the projects requirements in the project specs?
OK, Rochelle. I consider this fixed for 3.3 then. I will link the issue to the feature request for java project infrastructure.
VERIFIED
Resolved for 3.4.x or earlier, no new info since then -> closing.
Reorganization of java component