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 256490 - maven-surefire plugin 2.19 breaks running single test
Summary: maven-surefire plugin 2.19 breaks running single test
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 8.1
Hardware: PC Windows 7 x64
: P3 normal with 2 votes (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-10 10:19 UTC by deveth0
Modified: 2016-01-12 13:07 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description deveth0 2015-11-10 10:19:29 UTC
Hi all,

during an upgrade of our used maven-plugins, I stumbled into a problem with the combination of surefire and netbeans.
Currently a maven cmd like this is used to start a single test:

mvn -Dtest=de.dev.eth0.foo.BarTest test-compile surefire:test


this was fine since version 2.18 of the plugin but now package-names are nolonger supported{1] but you have to use the path instead:

mvn -Dtest=de/dev/eth0/foo/BarTest test-compile surefire:test

If you still use the old notation, no test is executed. The problem here is, that you are able to configure the "test" property in your projects properties but the only available placeholder is packageClassName: "test=${packageClassName}".

I'd love to see a placeholder which does not use package notation but the path so upgrades of the plugin can be used in netbeans too.

[1] https://issues.apache.org/jira/browse/SUREFIRE-1191
Comment 1 skygo 2016-01-12 12:37:04 UTC
Hi, is it possible to confirm that bug is corrected with surefire 2.19.1
Comment 2 milanka 2016-01-12 13:07:14 UTC
Running a single test works with Surefire 2.19.1.