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.
netbeans can only see source files exists under source folder "src" but in some cases there is a need for multiple source folders, for example in case there is a need to put application source files under "src" and unit tests under "test" folder. but netbeans can only use folder indicated by property ${src.dir} in nbproject/project.properties file.
*** Issue 138229 has been marked as a duplicate of this issue. ***
you seem to be doing something wrong. the test source folder are frequently used. And actually you shall be able to have as many source roots as you want. closing as works for me. please reopen with detailed steps to reproduce and a sample project demonstrating the problem.
sorry, I forgot to mention this problem is only with mobile projects.
ok, reassigning to mobility
Created attachment 71917 [details] Early draft of multiple source root support
I've attached a first draft of multiple project support. Here are issues that are pending: - Unintentional API change for CustomizerPanel (didn't realize it was in a public package) should be reverted - Includes a UI for adding multiple unit test roots as well, which should probably be gotten rid of (?) - After an existing mobility project has been opened in NetBeans with these patches, it cannot be opened in previous versions of NetBeans anymore (new XML namespace for project configuration data) What will take some thrashing out is finding any remaining code which assumes that there is only one source root. At any rate, it is a start. I will attach a build of the mobility project module; however, it is a rough draft. Therefore DO NOT USE THE ATTACHED MODULES ON ANY PROJECT YOU DO NOT HAVE A BACKUP OF.
will this be ready in release 6.5?
Definitely no. This is a high impact change
Tim, could you move all from this issue to this one http://www.netbeans.org/issues/show_bug.cgi?id=138749 ?
If bug 138749 is fixed, assuming we won't be looking to implement this any time soon.