For suite component module projects, of course it should be removed from the
suite's module list too.
High priority feature for the next release.
*** Issue 65514 has been marked as a duplicate of this issue. ***
Created attachment 25582 [details]
When the project of the same name was created immediately
after closing the project
and deleting the folder of the project outside IDE,
the error had occurred inside. messages.log is attached.
[ step ]
1. File > New Project >
Categories:NetBeans Plug-in Modules, Projects:Module Project
2. Next >
3. Next >
Code Name Base: org.myorg.myfirstmodule
4. Finish >
5. File > Close "MyFirstModule"
* The project folder "MyFirstModule" is deleted outside IDE.
* 1 to 4 is repeated.
* Here, the error was outputted to messages.log.
6. File > New File
Categories: NetBeans Module Development, File Types: Action
* Here, the Null Pointer exception has happened.
7. Next > Next > Next >
8. Class Name: MyFirstAction, Display Name: My First Action
* Even if it can do well, the error may be outputted.
copy/paste/rename/delete on module/suite as described in dupes.
*** Issue 66081 has been marked as a duplicate of this issue. ***
*** Issue 67021 has been marked as a duplicate of this issue. ***
*** Issue 67343 has been marked as a duplicate of this issue. ***
Just added [50cat] prefix because my issue is marked as duplicate of this one
*** Issue 67921 has been marked as a duplicate of this issue. ***
I would like to integrate for 5.1 M1. Presuambly also other similar tasks
(move/rename/copy). But could be worked on separately, I believe from the first
look at the Project API. Do not know that too much yet :)
NBM module done. Suite not yet.
Not sure if modules in NB cvs tree should be handle in some special way.
NbModuleProject.java; 1.134 -> 1.135;
Util.java; 1.25 -> 1.26;
ui/ModuleActions.java; 1.16 -> 1.17;
ui/SuiteLogicalView.java; 1.20 -> 1.21;
1. do the clean to allow a clean deletion
2. do not hardcode build.xml
3. deleting also .cvsignore which is generated under certain conditions
(question? - is this a good idea?)
test/unit/ui/ModuleOperationsTest.java; 1.2 -> 1.3;
ui/ModuleOperations.java; 1.1 -> 1.2;
Probably finished. Let's reopen and/or file a new bug. Tomasi or Zajo could you
test/comment this? Thanks.
- when module is deleted and is a suite component it is also removed
from it's suite and vice versa.
- when suite is deleted all of its suite component become standalone modules
- otherwise hopefully expected behaviour
ui/SuiteActions.java; 1.11 -> 1.12;
suite/SuiteProject.java; 1.26 -> 1.27;
ui/ModuleOperations.java; 1.2 -> 1.3;
minor comment - I'm not an UI expert, but delete module dialog seems too large
for me on Win XP (vertically - there's too much blank space under "also delete
> but delete module dialog seems too large
Yes, I agree. Please file a bug against projects module. This dialog is provided
> Yes, I agree. Please file a bug against projects module. This dialog is provided
> by them.
filed issue 70993.
great! thanks. Verified as feature. (bugs - if any - will be filed in separate
*** Issue 71906 has been marked as a duplicate of this issue. ***