Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 110312 - No way to define test roots for extra compilation units
No way to define test roots for extra compilation units
Product: apisupport
Classification: Unclassified
Component: Project
All All
: P3 (vote)
: 6.x
Assigned To: Jesse Glick
Depends on:
  Show dependency treegraph
Reported: 2007-07-19 15:48 UTC by Andrei Badea
Modified: 2007-07-19 18:29 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Badea 2007-07-19 15:48:54 UTC
There doesn't seem to be a way to define test roots for extra compilation units. I was expecting something like:

Comment 1 Jesse Glick 2007-07-19 17:08:12 UTC
Do you have a particular example (module) in mind?

Format change, so will not be considered for 6.0.
Comment 2 Milos Kleint 2007-07-19 17:30:30 UTC
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.
Comment 3 Andrei Badea 2007-07-19 17:33:18 UTC
Yes: db. I tried to generate a test for a class in libsrc.
Comment 4 Jesse Glick 2007-07-19 18:03:40 UTC
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).
Comment 5 David Vancouvering 2007-07-19 18:11:00 UTC
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
Comment 6 Jesse Glick 2007-07-19 18:29:21 UTC
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 CVS, nbdev is fine. (For external modules it is preferred to

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo