[jira] Updated: (MPH-32) "medium" mode should be the default for help:describe

[ http://jira.codehaus.org/browse/MPH-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated MPH-32: Description: Right now if you "mvn help:describe -Dplugin=compiler" you'll see this: {noformat} [INFO] Plugin: 'org.

[jira] Created: (MPH-32) "medium" mode should be the default for help:describe

"medium" mode should be the default for help:describe - Key: MPH-32 URL: http://jira.codehaus.org/browse/MPH-32 Project: Maven 2.x Help Plugin Issue Type: Improvement Reporter:

[jira] Created: (MPH-33) Help plugin should refer to "goal" not "mojo"

Help plugin should refer to "goal" not "mojo" - Key: MPH-33 URL: http://jira.codehaus.org/browse/MPH-33 Project: Maven 2.x Help Plugin Issue Type: Improvement Reporter: Dan Fabulich

[jira] Updated: (MPH-34) Add a new help goal that describes the current lifecycle bindings

[ http://jira.codehaus.org/browse/MPH-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated MPH-34: Description: There should be a goal that examines the current POM's lifecycle and prints out a list of phases and li

[jira] Created: (MDEP-141) there should be a way to purge all snapshots

there should be a way to purge all snapshots Key: MDEP-141 URL: http://jira.codehaus.org/browse/MDEP-141 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: purge-lo

[jira] Commented: (MDEP-141) there should be a way to purge all snapshots

[ http://jira.codehaus.org/browse/MDEP-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122361 ] Dan Fabulich commented on MDEP-141: --- Well, I only filed it here because "purge-local-repository" is a goal on this plugin; I

[jira] Closed: (SUREFIRE-450) Verification test failure: Invalid mavenProfile entry. Missing one or more fields: {localRepository}

[ http://jira.codehaus.org/browse/SUREFIRE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-450. - Resolution: Cannot Reproduce I don't reproduce this. What version of Maven are you using? What OS?

[jira] Updated: (SUREFIRE-449) In multi-module projects, all tests are run for each module in the module tree

[ http://jira.codehaus.org/browse/SUREFIRE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-449: -- Fix Version/s: 2.4.2 Thanks for filing this bug; I noticed it too but thought it was just SUREFIRE

[jira] Commented: (SUREFIRE-450) Verification test failure: Invalid mavenProfile entry. Missing one or more fields: {localRepository}

[ http://jira.codehaus.org/browse/SUREFIRE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122463 ] Dan Fabulich commented on SUREFIRE-450: --- Notably, this stacktrace indicates that it's having problems reading your s

[jira] Updated: (SUREFIRE-446) Surefire fails to capture TestNG results when forkMode=always

[ http://jira.codehaus.org/browse/SUREFIRE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-446: -- Fix Version/s: 2.4.2 Repro'd. > Surefire fails to capture TestNG results when forkMode=always > --

[jira] Created: (SUREFIRE-451) ManifestJarWriter should use java.util.jar.Manifest

ManifestJarWriter should use java.util.jar.Manifest --- Key: SUREFIRE-451 URL: http://jira.codehaus.org/browse/SUREFIRE-451 Project: Maven Surefire Issue Type: Improvement Components:

[jira] Commented: (SUREFIRE-445) Surefire-Booter Manifest not correct

[ http://jira.codehaus.org/browse/SUREFIRE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122487 ] Dan Fabulich commented on SUREFIRE-445: --- There's really two separate changes in here: one of them is to just add the

[jira] Commented: (SUREFIRE-451) ManifestJarWriter should use java.util.jar.Manifest

[ http://jira.codehaus.org/browse/SUREFIRE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122489 ] Dan Fabulich commented on SUREFIRE-451: --- Notably, I find that the difference between the two is that java.util.jar.M

[jira] Updated: (SUREFIRE-451) ManifestJarWriter should use java.util.jar.Manifest

[ http://jira.codehaus.org/browse/SUREFIRE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-451: -- Fix Version/s: 2.x > ManifestJarWriter should use java.util.jar.Manifest >

[jira] Closed: (SUREFIRE-445) Surefire-Booter Manifest not correct

[ http://jira.codehaus.org/browse/SUREFIRE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-445. - Resolution: Fixed Fix Version/s: 2.4.2 > Surefire-Booter Manifest not correct > --

[jira] Closed: (SUREFIRE-448) @Before, @After, @BeforeClass, @AfterClass do not seem to be functioning as of 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-448. - Resolution: Cannot Reproduce I can't reproduce this failure. I attached a sample minimal Maven proje

[jira] Updated: (SUREFIRE-448) @Before, @After, @BeforeClass, @AfterClass do not seem to be functioning as of 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-448: -- Attachment: surefire448.zip > @Before, @After, @BeforeClass, @AfterClass do not seem to be function

[jira] Commented: (SUREFIRE-449) In multi-module projects, all tests are run for each module in the module tree

[ http://jira.codehaus.org/browse/SUREFIRE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122513 ] Dan Fabulich commented on SUREFIRE-449: --- This is happening because I added @aggregator to surefire-report in order to

[jira] Updated: (SUREFIRE-446) Surefire fails to capture TestNG results when forkMode=always

[ http://jira.codehaus.org/browse/SUREFIRE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-446: -- Fix Version/s: (was: 2.4.2) 2.x This is trickier than it looks... I'm not 1

[jira] Commented: (SUREFIRE-449) In multi-module projects, all tests are run for each module in the module tree

[ http://jira.codehaus.org/browse/SUREFIRE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122704 ] Dan Fabulich commented on SUREFIRE-449: --- I stripped off @aggregator in revision 619233; that seems to fix your proble

[jira] Closed: (SUREFIRE-449) In multi-module projects, all tests are run for each module in the module tree

[ http://jira.codehaus.org/browse/SUREFIRE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-449. - Resolution: Fixed > In multi-module projects, all tests are run for each module in the module tree >

[jira] Updated: (MJAVADOC-171) Modules in multi-module projects are "built" too often

[ http://jira.codehaus.org/browse/MJAVADOC-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated MJAVADOC-171: -- Attachment: mjavadoc171.patch FYI, I can't get maven-javadoc-plugin to "mvn install" from trunk (I

[jira] Commented: (MJAVADOC-137) javadoc:javadoc always runs as "aggregator"

[ http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122843 ] Dan Fabulich commented on MJAVADOC-137: --- I'm pretty sure MNG-2184 is to blame here; it seems clear that reporting pl

[jira] Commented: (SUREFIRE-452) suitename always = "TestSuite" even if defined as property

[ http://jira.codehaus.org/browse/SUREFIRE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122859 ] Dan Fabulich commented on SUREFIRE-452: --- I reproduce the problem, but I find that the integration test TestNgSuiteXm

[jira] Updated: (SUREFIRE-452) suitename always = "TestSuite" even if defined as property

[ http://jira.codehaus.org/browse/SUREFIRE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-452: -- Fix Version/s: 2.x Targeting for 2.x (this won't block 2.4.2 coming out) but if you can provide an

[jira] Closed: (SUREFIRE-451) ManifestJarWriter should use java.util.jar.Manifest

[ http://jira.codehaus.org/browse/SUREFIRE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-451. - Resolution: Fixed Fix Version/s: (was: 2.x) 2.4.2 Fixed in revision 619

[jira] Closed: (SUREFIRE-453) unable to run spring/jpa/dao test with derby starting with surefire 2.4.x

[ http://jira.codehaus.org/browse/SUREFIRE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-453. - Resolution: Cannot Reproduce I can't reproduce this; I think I need more environment information. Wh

[jira] Commented: (SUREFIRE-452) suitename always = "TestSuite" even if defined as property

[ http://jira.codehaus.org/browse/SUREFIRE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123168 ] Dan Fabulich commented on SUREFIRE-452: --- Hmmm... Just reviewing this, I note that it only works with a directory tes

[jira] Commented: (SUREFIRE-453) unable to run spring/jpa/dao test with derby starting with surefire 2.4.x

[ http://jira.codehaus.org/browse/SUREFIRE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123292 ] Dan Fabulich commented on SUREFIRE-453: --- Repro'd. > unable to run spring/jpa/dao test with derby starting with suref

[jira] Updated: (SUREFIRE-443) Provide option to merge test classpath into one directory

[ http://jira.codehaus.org/browse/SUREFIRE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-443: -- Description: Please provide an option for the test classpath to be merged into one directory. Mave

[jira] Closed: (SUREFIRE-455) XML delimiter characters in attribute and text content are escaped twice.

[ http://jira.codehaus.org/browse/SUREFIRE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-455. - Resolution: Fixed Fix Version/s: 2.4.2 Thanks for your work here. We actually have an integra

[jira] Updated: (SUREFIRE-456) Surefire doubly XML-escapes non-visible control characters

[ http://jira.codehaus.org/browse/SUREFIRE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-456: -- Fix Version/s: Future > Surefire doubly XML-escapes non-visible control characters > --

[jira] Created: (SUREFIRE-456) Surefire doubly XML-escapes non-visible control characters

Surefire doubly XML-escapes non-visible control characters -- Key: SUREFIRE-456 URL: http://jira.codehaus.org/browse/SUREFIRE-456 Project: Maven Surefire Issue Type: Bug Compo

[jira] Closed: (SUREFIRE-453) unable to run spring/jpa/dao test with derby starting with surefire 2.4.x

[ http://jira.codehaus.org/browse/SUREFIRE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-453. - Resolution: Won't Fix The problem with this test has to do with the useSystemClassLoader configurati

[jira] Updated: (SUREFIRE-456) Surefire doubly XML-escapes non-visible control characters

[ http://jira.codehaus.org/browse/SUREFIRE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-456: -- Description: It's illegal to include a non-visible control character in XML, even as a character e

[jira] Commented: (SUREFIRE-456) Surefire doubly XML-escapes non-visible control characters

[ http://jira.codehaus.org/browse/SUREFIRE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123430 ] Dan Fabulich commented on SUREFIRE-456: --- To repro: run Surefire224WellFormedXmlFailuresTest. > Surefire doubly XML-e

[jira] Updated: (SUREFIRE-457) TestNG should log on the console before/after every test class

[ http://jira.codehaus.org/browse/SUREFIRE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-457: -- Fix Version/s: Future > TestNG should log on the console before/after every test class > --

[jira] Created: (SUREFIRE-457) TestNG should log on the console before/after every test class

TestNG should log on the console before/after every test class -- Key: SUREFIRE-457 URL: http://jira.codehaus.org/browse/SUREFIRE-457 Project: Maven Surefire Issue Type: Wish

[jira] Commented: (SUREFIRE-452) suitename always = "TestSuite" even if defined as property

[ http://jira.codehaus.org/browse/SUREFIRE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123962 ] Dan Fabulich commented on SUREFIRE-452: --- Two points. 1) I find it hard to believe that you're "blocked" by this bug.

[jira] Closed: (SUREFIRE-452) suitename always = "TestSuite" even if defined as property

[ http://jira.codehaus.org/browse/SUREFIRE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-452. - Resolution: Fixed Fix Version/s: (was: 2.x) 2.4.2 Ah, whatever. I fixe

[jira] Updated: (SUREFIRE-458) alternative test-class scanner (by type filter)

[ http://jira.codehaus.org/browse/SUREFIRE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-458: -- Fix Version/s: 2.x > alternative test-class scanner (by type filter) > ---

[jira] Commented: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124423 ] Dan Fabulich commented on SUREFIRE-459: --- Rather than just grabbing the current latest (which might be broken for some

[jira] Closed: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-459. - Resolution: Fixed Marking Fixed > Integration test using Jetty and JSP 2.1 fails after update to >

[jira] Commented: (SUREFIRE-448) @Before, @After, @BeforeClass, @AfterClass do not seem to be functioning as of 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124549 ] Dan Fabulich commented on SUREFIRE-448: --- That's weird. I see: Running junit4.WeatherMessageGeneratorCallableTest >>

[jira] Updated: (SUREFIRE-448) @Before, @After, @BeforeClass, @AfterClass do not seem to be functioning as of 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-448: -- Attachment: surefire448.zip updated project > @Before, @After, @BeforeClass, @AfterClass do not se

[jira] Closed: (SUREFIRE-448) @Before, @After, @BeforeClass, @AfterClass do not seem to be functioning as of 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-448. - Resolution: Cannot Reproduce Your log states that you're not using Surefire 2.4; you're using Surefir

[jira] Created: (MRELEASE-324) There should be a way to update POM version numbers without tagging/branching

There should be a way to update POM version numbers without tagging/branching - Key: MRELEASE-324 URL: http://jira.codehaus.org/browse/MRELEASE-324 Project: Maven 2.x Release

[jira] Closed: (SUREFIRE-462) Running Surefire with TestNG fails

[ http://jira.codehaus.org/browse/SUREFIRE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-462. - Resolution: Won't Fix This is a known issue with Surefire 2.3, fixed in 2.4. I recommend the latest

[jira] Closed: (SUREFIRE-464) Default for failIfNoTests should be false

[ http://jira.codehaus.org/browse/SUREFIRE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-464. - Resolution: Won't Fix I think you've made some incorrect assumptions about the way failIfNoTests wor

[jira] Created: (SUREFIRE-474) Allow TestNG to use its built-in HTMLReporter

Allow TestNG to use its built-in HTMLReporter - Key: SUREFIRE-474 URL: http://jira.codehaus.org/browse/SUREFIRE-474 Project: Maven Surefire Issue Type: Improvement Reporter: Dan Fabulic

[jira] Updated: (SUREFIRE-474) Allow TestNG to use its built-in HTMLReporter

[ http://jira.codehaus.org/browse/SUREFIRE-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-474: -- Fix Version/s: 2.5 > Allow TestNG to use its built-in HTMLReporter > --

[jira] Updated: (SUREFIRE-457) TestNG should log on the console before/after every test class

[ http://jira.codehaus.org/browse/SUREFIRE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-457: -- Attachment: testNGListenerTest.zip Jason Chaffee claims that you can get the right thing with onSta

[jira] Closed: (SUREFIRE-471) Infinite loop when ERROR is detected

[ http://jira.codehaus.org/browse/SUREFIRE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-471. - Resolution: Incomplete I can't reproduce this issue yet, so please reopen the bug with a reproducible

[jira] Closed: (SUREFIRE-469) test environment is not share between dependent modules

[ http://jira.codehaus.org/browse/SUREFIRE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-469. - Resolution: Incomplete This bug description doesn't contain enough information for me to reproduce th

[jira] Updated: (SUREFIRE-475) Classloader getResource() returns resource from wrong directory

[ http://jira.codehaus.org/browse/SUREFIRE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-475: -- Description: In upgrading from version 2.3 to 2.4.2, we encountered a different behaviour in class

[jira] Closed: (SUREFIRE-475) Classloader getResource() returns resource from wrong directory

[ http://jira.codehaus.org/browse/SUREFIRE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-475. - Resolution: Cannot Reproduce As mentioned, we've got an integration test checked in that verifies thi

[jira] Closed: (SUREFIRE-466) IsolatedClassLoader should also delegate resource loading

[ http://jira.codehaus.org/browse/SUREFIRE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-466. - Resolution: Incomplete What are the symptoms of this bug? Can you provide an example minimal Maven

[jira] Closed: (SUREFIRE-340) Resource classpaths differ if project has flat structure, causing MappingExceptions and more.

[ http://jira.codehaus.org/browse/SUREFIRE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-340. - Resolution: Cannot Reproduce Yup, just tried it with Maven 2.0.8 and Surefire 2.4.2. (All I did was

[jira] Commented: (SUREFIRE-463) ClassCastException when using testng suiteXmlFile

[ http://jira.codehaus.org/browse/SUREFIRE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128811#action_128811 ] Dan Fabulich commented on SUREFIRE-463: --- Well, I think I like the idea of this patch, but I'm

[jira] Reopened: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich reopened SUREFIRE-459: --- Assignee: Dan Fabulich We just found a repro case for this at Redfin. I'll attach a sample tha

[jira] Closed: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-459. - Resolution: Fixed Fix Version/s: 2.5 Fixed in revision 642046. By default forkMode=once and

[jira] Created: (MAVENUPLOAD-2012) TestNG 5.8

TestNG 5.8 -- Key: MAVENUPLOAD-2012 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2012 Project: maven-upload-requests Issue Type: Task Reporter: Dan Fabulich Attachments: testng-5.8-bundle.jar TestNG 5.8. I'

[jira] Commented: (MAVENUPLOAD-2012) TestNG 5.8

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130540#action_130540 ] Dan Fabulich commented on MAVENUPLOAD-2012: --- The Contributor URL, for the record, is

[jira] Created: (SUREFIRE-488) Document TestNG listeners/reporters

Document TestNG listeners/reporters --- Key: SUREFIRE-488 URL: http://jira.codehaus.org/browse/SUREFIRE-488 Project: Maven Surefire Issue Type: Task Components: documentation, TestNG support

[jira] Closed: (SUREFIRE-487) We're using DynamicJasper to create reports in our web application. DynamicJasper creates a java report file at runtime and compiles it. It works fine in the application

[ http://jira.codehaus.org/browse/SUREFIRE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-487. - Resolution: Cannot Reproduce I get compile errors when I try to build your project; I'm unable to run

[jira] Created: (SUREFIRE-489) Document classpath issues

Document classpath issues - Key: SUREFIRE-489 URL: http://jira.codehaus.org/browse/SUREFIRE-489 Project: Maven Surefire Issue Type: Task Reporter: Dan Fabulich Fix For: 2.4.3 This doc should

[jira] Updated: (SUREFIRE-489) Document classpath issues

[ http://jira.codehaus.org/browse/SUREFIRE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-489: -- Fix Version/s: 2.4.3 > Document classpath issues > - > > Ke

[jira] Closed: (SUREFIRE-481) java.lang.NoSuchMethodError when forking on a 1.3 JDK

[ http://jira.codehaus.org/browse/SUREFIRE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-481. - Resolution: Fixed Fix Version/s: 2.4.3 This is indeed fixed. I'll try to push out a snapshot

[jira] Updated: (SUREFIRE-468) When tests timeout, report files on disk are incorrect

[ http://jira.codehaus.org/browse/SUREFIRE-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-468: -- Fix Version/s: 2.5 Summary: When tests timeout, report files on disk are incorrect (was:

[jira] Updated: (SUREFIRE-472) Add support for view by groups in the surefire report

[ http://jira.codehaus.org/browse/SUREFIRE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-472: -- Fix Version/s: Future This would be handy. Probably more likely when we get group support for JUni

[jira] Created: (SUREFIRE-490) Provide an option to use simplified classloading

Provide an option to use simplified classloading Key: SUREFIRE-490 URL: http://jira.codehaus.org/browse/SUREFIRE-490 Project: Maven Surefire Issue Type: Improvement Components: class

[jira] Updated: (SUREFIRE-490) Provide an option to use simplified classloading

[ http://jira.codehaus.org/browse/SUREFIRE-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-490: -- Fix Version/s: 2.5 > Provide an option to use simplified classloading > ---

[jira] Created: (SUREFIRE-491) All system properties from Maven process are copied to forked Surefire process

All system properties from Maven process are copied to forked Surefire process -- Key: SUREFIRE-491 URL: http://jira.codehaus.org/browse/SUREFIRE-491 Project: Maven Surefire

[jira] Closed: (SUREFIRE-461) -Xbootclasspath specified in not passed to forked JVM

[ http://jira.codehaus.org/browse/SUREFIRE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-461. - Resolution: Duplicate Yes, I can reproduce your test failure. In fact, I think this is just a speci

[jira] Commented: (SUREFIRE-491) All system properties from Maven process are copied to forked Surefire process

[ http://jira.codehaus.org/browse/SUREFIRE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132897#action_132897 ] Dan Fabulich commented on SUREFIRE-491: --- This is happening due to the fix for SUREFIRE-121.

[jira] Closed: (SUREFIRE-476) Skipped test should not be considered as "failed test"

[ http://jira.codehaus.org/browse/SUREFIRE-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-476. - Resolution: Won't Fix I don't think this patch is logically correct. Logically, a test can have thr

[jira] Updated: (SUREFIRE-482) Surefire tries to run JUnit4 tests that contain no @Test annotations

[ http://jira.codehaus.org/browse/SUREFIRE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-482: -- Fix Version/s: 2.5 > Surefire tries to run JUnit4 tests that contain no @Test annotations > ---

[jira] Created: (MNG-3556) XML entity not supported in Maven 2

XML entity not supported in Maven 2 --- Key: MNG-3556 URL: http://jira.codehaus.org/browse/MNG-3556 Project: Maven 2 Issue Type: Bug Components: General Reporter: Dan Fabulich At

[jira] Closed: (SUREFIRE-486) Exlude tests via an external exlude file

[ http://jira.codehaus.org/browse/SUREFIRE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-486. - Resolution: Won't Fix I don't think that's the feature you want; there's a better way to do it. JUn

[jira] Updated: (SUREFIRE-479) @BeforeClass and @AfterClass on parent class are not executed

[ http://jira.codehaus.org/browse/SUREFIRE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-479: -- Attachment: surefire479.zip > @BeforeClass and @AfterClass on parent class are not executed > -

[jira] Closed: (SUREFIRE-479) @BeforeClass and @AfterClass on parent class are not executed

[ http://jira.codehaus.org/browse/SUREFIRE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-479. - Resolution: Cannot Reproduce I can't reproduce this. I've attached a sample Maven project that follo

[jira] Updated: (SUREFIRE-465) Add numeric option for forkmode param

[ http://jira.codehaus.org/browse/SUREFIRE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-465: -- Fix Version/s: Future Perhaps more plausible might be to fork a process on a per-package basis. >

[jira] Updated: (SUREFIRE-491) All system properties from Maven process are copied to forked Surefire process

[ http://jira.codehaus.org/browse/SUREFIRE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-491: -- Affects Version/s: (was: 2.5) 2.4.3 Fix Version/s: 2.5 > All sys

[jira] Updated: (SUREFIRE-488) Document TestNG listeners/reporters

[ http://jira.codehaus.org/browse/SUREFIRE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-488: -- Fix Version/s: 2.4.3 > Document TestNG listeners/reporters > --- >

[jira] Updated: (SUREFIRE-463) ClassCastException when using testng suiteXmlFile and forkMode=always

[ http://jira.codehaus.org/browse/SUREFIRE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-463: -- Fix Version/s: 2.4.3 Summary: ClassCastException when using testng suiteXmlFile and forkM

[jira] Updated: (SUREFIRE-480) Improper TestCase classes incorrectly reported as a failure of the TestSuite class

[ http://jira.codehaus.org/browse/SUREFIRE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-480: -- Fix Version/s: Future This may be a bug in JUnit itself rather than in Surefire. The Java stacktra

[jira] Updated: (SUREFIRE-473) Documentation for additionalClassPath feature

[ http://jira.codehaus.org/browse/SUREFIRE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-473: -- Fix Version/s: 2.4.3 > Documentation for additionalClassPath feature >

[jira] Created: (SUREFIRE-492) Allow "test" parameter to override suiteXmlFiles

Allow "test" parameter to override suiteXmlFiles Key: SUREFIRE-492 URL: http://jira.codehaus.org/browse/SUREFIRE-492 Project: Maven Surefire Issue Type: Bug Components: TestNG suppor

[jira] Updated: (SUREFIRE-492) Allow "test" parameter to override suiteXmlFiles

[ http://jira.codehaus.org/browse/SUREFIRE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-492: -- Fix Version/s: 2.4.3 > Allow "test" parameter to override suiteXmlFiles > -

[jira] Updated: (SUREFIRE-477) Issue with redirectTestOutputToFile and unit test with System.out.print

[ http://jira.codehaus.org/browse/SUREFIRE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-477: -- Attachment: surefire477.zip > Issue with redirectTestOutputToFile and unit test with System.out.pri

[jira] Closed: (SUREFIRE-477) Issue with redirectTestOutputToFile and unit test with System.out.print

[ http://jira.codehaus.org/browse/SUREFIRE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-477. - Resolution: Cannot Reproduce I can't reproduce this issue. I've attached a simple maven project that

[jira] Created: (SUREFIRE-493) UrlUtilsTest fails

UrlUtilsTest fails -- Key: SUREFIRE-493 URL: http://jira.codehaus.org/browse/SUREFIRE-493 Project: Maven Surefire Issue Type: Bug Environment: Maven version: 2.0.8, Java version: 1.6.0_02, OS name: "windows xp" vers

[jira] Updated: (SUREFIRE-485) Support AntUnit XML output

[ http://jira.codehaus.org/browse/SUREFIRE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-485: -- Fix Version/s: 2.4.3 > Support AntUnit XML output > -- > >

[jira] Updated: (SUREFIRE-493) UrlUtilsTest fails

[ http://jira.codehaus.org/browse/SUREFIRE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-493: -- Fix Version/s: 2.4.3 > UrlUtilsTest fails > -- > > Key: SUREFIRE-49

[jira] Closed: (SUREFIRE-486) Exlude tests via an external exlude file

[ http://jira.codehaus.org/browse/SUREFIRE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-486. - Resolution: Won't Fix That page doesn't have anything to do with testing, though I'm quite familiar

[jira] Closed: (SUREFIRE-494) Add support to set listener to testNG runner

[ http://jira.codehaus.org/browse/SUREFIRE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-494. - Resolution: Not A Bug Surefire already supports configuring custom listeners/reporters. Unfortunate

[jira] Closed: (SUREFIRE-477) Issue with redirectTestOutputToFile and unit test with System.out.print

[ http://jira.codehaus.org/browse/SUREFIRE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-477. - Resolution: Cannot Reproduce Something is wrong with your attached file! It's 0.0 kb. Try again? >

[jira] Closed: (SUREFIRE-493) UrlUtilsTest fails

[ http://jira.codehaus.org/browse/SUREFIRE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-493. - Resolution: Fixed Fixed in revision 652176. > UrlUtilsTest fails > -- > >

[jira] Closed: (SUREFIRE-485) Support AntUnit XML output

[ http://jira.codehaus.org/browse/SUREFIRE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-485. - Resolution: Fixed Patch submitted revision 652186. Thanks! > Support AntUnit XML output > -

[jira] Closed: (SUREFIRE-463) ClassCastException when using testng suiteXmlFile and forkMode=always

[ http://jira.codehaus.org/browse/SUREFIRE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-463. - Resolution: Fixed Fixed revision 652188. > ClassCastException when using testng suiteXmlFile and for

<    1   2   3   4   5   6   >