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.
Summary: | Maven issues in 6.7 that were not present in 6.5 (run test class, system properties) | ||
---|---|---|---|
Product: | projects | Reporter: | ebiel <ebiel> |
Component: | Maven | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
ebiel
2009-07-02 14:51:06 UTC
1. In 6.7 you should use the "Test file" action for testing, rather than "Run file" (which executes main class), the Test file action is missing in editor's popup (issue 167267). 2. Is the test executed via the quick runner/compile on save? you would notice by having non-maven output in the output window when running the test. If so, can you try turning Compile on Save off (in project properties window) and retry? Okay, compile on save option definitely plays a role here, at least for test classes (see point 3): 1. Compile on save: test execution only I run the test class using 'Test File' and for about one minute (!) nothing at all happens. Then, the Test Results window pops up and the test is executed. System properties defined in the pom.xml as described in the description do not work. 2. Compile on save: disabled I run the test class using 'Test File', the Test Results window immediately pops up and the test is executed. System properties defined in the pom.xml do work. 3. Compile on save: disabled I run a class with a main method (no test class, lives in source tree not in the test tree of the project) using 'Run File'. System properties defined in the pom.xml do not work. Thanks for the quick reply! re 1. the long delay probably means the build/run was executing in the output window that was hidden. the issue described here is a duplicate of #168036. re 3. probably a problem in exec-maven-plugin, or your configuration of the plugin. Not really netbeans related it seems. closing as duplicate of #168036. *** This issue has been marked as a duplicate of 168036 *** |