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.

Bug 57732 - [41cat] Cannot compile junit tests in web app.
Summary: [41cat] Cannot compile junit tests in web app.
Status: CLOSED DUPLICATE of bug 58230
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Project (show other bugs)
Version: 4.x
Hardware: All Linux
: P2 blocker (vote)
Assignee: Radko Najman
Depends on:
Reported: 2005-04-11 15:50 UTC by mdm42
Modified: 2005-07-13 14:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description mdm42 2005-04-11 15:50:38 UTC
Junit tests added to a web project cannot be compiled: compile action is
disabled (menus, keyboard).

Further there seems to be no UI for setting destination directory where unit
tests get compiled to.

The test directory is set using the Project Options UI as a Test Package Folder.

Tried manually setting "have.tests", "build.test.classes.dir"
and "build.test.results.dir" to suitable values, but no luck.

Have searched and searched website and docs.... :-(
Comment 1 zikmund 2005-04-11 15:57:03 UTC
It has been fixed in early March - see duplicate issue 55798.
If it doesn't work for you in latest builds, feel free to reopen. Thanks for report!

*** This issue has been marked as a duplicate of 55798 ***
Comment 2 mdm42 2005-04-25 10:00:05 UTC
In NB4.1rc1 (build 200504200735):

Can now build unit test, but they won't execute, since the target dir does not
get set anywhere that I can find.  As a result tests are compiled to the project
root dir which is not in the runtime classpath, resulting ClassNotFoundException.
Comment 3 zikmund 2005-04-25 10:09:30 UTC
Which project type is it?
If your project is 4.0 project, it can be duplicate of issue 58230 (see
workaround there). I'll check Web project with existing sources.
Comment 4 mdm42 2005-04-25 10:43:56 UTC
Yep -- seems to be the same issue as 58230:  It is a web project imported from
4.0.  Thanks for the workaround.

*** This issue has been marked as a duplicate of 58230 ***