Re: sources vs. Java packages roots
Vitezslav Stejskal <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.modules.projects.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Radim, Radim Kubacki wrote: > projects gurus, > > is it design or (known?) bug that there is no relationship between > sources and Java packages roots? Hmm, so far it is as designed. > > Namely when I add directory containing sources and mark some of > subdirs as Java packages roots these are not removed from project when > I remove this sources diretory. It means that Add + Remove doesn't > return my project to previous state. Alternatively we could make this process two step: 1. user can add sources (files or folders) to the project, in case of folders everything underneath belongs to the project too 2. when selecting files/folders for becoming java roots (any role) the presented filechooser would allow to browse only files/folders added in step #1 I am not sure about all consequences of this approach, but do you think it would be more appropriate? > Also it is not clear to me why predefined java package root is not > contained in some sources (maybe it is better not to clutter the UI > with an additional sources folder). > > Looks unnatural to me so please keep this mail as some kind of > usability feedback. Sure, thanks for your feedback. -vita