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 234235 - Maven Test Rerun failed
Summary: Maven Test Rerun failed
Status: RESOLVED INVALID
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.4
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-11 07:59 UTC by bht
Modified: 2013-08-20 17:22 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bht 2013-08-11 07:59:29 UTC
Product Version: NetBeans IDE Dev (Build 201308092300)
Java: 1.7.0_25; Java HotSpot(TM) Client VM 23.25-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_25-b17
System: Windows XP version 5.1 running on x86; Cp1252; en_NZ (nb)

How to reproduce:

Use a large project. Please download Wicket as follows from the command line (I could not do it with the NetBeans IDE):

git clone http://git-wip-us.apache.org/repos/asf/wicket.git -b build/wicket-6.9.2-SNAPSHOT

- Open the "Wicket Parent" project in the IDE
- Ensure that compile on save is enabled
- Modify in pom.xml <maven.surefire.version>2.15</maven.surefire.version>
  ( I did this to stay clear of issue 214334, http://jira.codehaus.org/browse/SUREFIRE-745 and fixed in upcoming 2.13 of maven surefire plugin)
- From Modules, open the "Wicket Core" project
- Go to Type|Component (org.apache.wicket.Component)
- Replace 2 instances of page.isPageStateless with page.isBookmarkable and save
- In Projects window, select "Wicket Core" right click | Test
- The "Test Results" window should show more than 50 test failures
- Click the button "Rerun Failed"

I get this error:

--- maven-surefire-plugin:2.15:test (default-test) @ wicket-core ---
Surefire report directory: C:\bt\java\servlet\Wicket\source-6\wicket\wicket-core\target\surefire-reports
Using configured provider org.apache.maven.surefire.junitcore.JUnitCoreProvider
parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false

-------------------------------------------------------
 T E S T S
-------------------------------------------------------

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time: 1:44.016s
Finished at: Sun Aug 11 19:52:29 NZST 2013
Final Memory: 15M/83M
------------------------------------------------------------------------
Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test (default-test) on project wicket-core: No tests were executed!  (Set -DfailIfNoTests=false to ignore this error.) -> [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please read the following articles:
[Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Comment 1 Milos Kleint 2013-08-20 12:04:56 UTC
there doesn't appear to be a branch named -b build/wicket-6.9.2-SNAPSHOT in the wicket git repo.. which branch is a viable alternative?
Comment 2 Milos Kleint 2013-08-20 12:34:18 UTC
what is the header line of the re-run build? I mean the gray lines that the IDE prints out with the content of cmd line config passed to the maven JVM?
Comment 3 bht 2013-08-20 17:14:25 UTC
My apologies. I cannot reproduce this with the latest build. Good news :)