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.
There doesn't seem to be a way to define test roots for extra compilation units. I was expecting something like: <extra-compilation-root> <package-root>libsrc</package-root> <test-root>libtest</test-root> ...
Do you have a particular example (module) in mind? Format change, so will not be considered for 6.0.
extra compilation unit itself feels a bit like a hack to me (a semi-project within a project). This enhancement reinfoces that feeling. I'd rather see that we allow linking nbmodule projects with regular java projects somehow and the extra compilation root becomes a separate projects.. just my 2 cents.
Yes: db. I tried to generate a test for a class in libsrc.
To abadea: you can always create a test class directly in the desired location using the NFW. Defining <test-root>s doesn't buy you a whole lot; it just sets up the right default location for the JUnit wizards. You still have to write the Ant plumbing yourself anyway. To mkleint: yes, <e-c-u> is sort of a hack, and it may well make sense to split the extra root off into its own project. (Note that some ECUs have a compile-time dependency on the module, which would make this a little trickier, though still possible: lib/build.xml#jar would dep on build.xml#jar but build.xml#netbeans-extra would dep on lib/build.xml#jar.) You can already split off such roots into separate j2seproject's if you prefer. See also issue #70894 which would make such setups a little easier (by removing the need to modify your module project's build.xml).
Sorry, what's "NFW"? And what do you mean by "setting up the Ant plumbing?" I'm the one trying to create this unit test for a separate source directory, so I'd appreciate your guidance. Is there a mailing list where I can ask this question?
New File Wizard. "Ant plumbing" - just custom build.xml modifications. I have never seen someone write tests for ECUs so there are no conventions or examples I can point you to. There is XTest-based infrastructure for writing tests for module code, but I don't think it will work for ECUs. I tend to agree with Miloš that if your extra root is complicated enough that it needs, you should probably just make it a separate project. I am therefore rejecting this RFE. For assistance configuring module projects in netbeans.org CVS, nbdev is fine. (For external modules it is preferred to use dev@openide.netbeans.org.)