[jira] Commented: (MSHADE-8) Shade plugin will cheerfully relocate your own classes

[ https://jira.codehaus.org/browse/MSHADE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272199#comment-272199 ] Dan Fabulich commented on MSHADE-8: --- I filed this issue and I agree that it's an enhancement, but I

[jira] (SUREFIRE-514) Provide a way to skip a project's tests if nothing has changed

[ https://jira.codehaus.org/browse/SUREFIRE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356173#comment-356173 ] Dan Fabulich commented on SUREFIRE-514: --- I don't think I understand your comment. 1) I agr

[jira] Created: (SUREFIRE-595) Add surefire:force-test mojo to postpone tests

Add surefire:force-test mojo to postpone tests -- Key: SUREFIRE-595 URL: http://jira.codehaus.org/browse/SUREFIRE-595 Project: Maven Surefire Issue Type: New Feature Reporter: Dan Fabul

[jira] Commented: (SUREFIRE-595) Add surefire:force-test mojo to postpone tests

[ http://jira.codehaus.org/browse/SUREFIRE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205848#action_205848 ] Dan Fabulich commented on SUREFIRE-595: --- Note that this is also useful in single-threaded bui

[jira] Updated: (SUREFIRE-595) Add surefire:force-test mojo to postpone tests

[ http://jira.codehaus.org/browse/SUREFIRE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-595: -- Comment: was deleted (was: Note that this is also useful in single-threaded builds; in many cases

[jira] (SUREFIRE-1041) JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace

[ https://jira.codehaus.org/browse/SUREFIRE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-1041: --- Attachment: SUREFIRE-1041.patch > JUnit47 provider: Exception in JUnit Runner can crash tes

[jira] (SUREFIRE-1041) JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace

Dan Fabulich created SUREFIRE-1041: -- Summary: JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace Key: SUREFIRE-1041 URL: https://jira.codehaus.org/browse/SUREFIRE-1041

[jira] (SUREFIRE-1041) JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace

[ https://jira.codehaus.org/browse/SUREFIRE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-1041: --- Attachment: SUREFIRE-1041-testcase.zip > JUnit47 provider: Exception in JUnit Runner can cr

[jira] (SUREFIRE-1041) JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace

[ https://jira.codehaus.org/browse/SUREFIRE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335641#comment-335641 ] Dan Fabulich commented on SUREFIRE-1041: This came up when we encountered this PowerMock

[jira] Created: (MENFORCER-63) Fail the build on reactor dependency divergence

Fail the build on reactor dependency divergence --- Key: MENFORCER-63 URL: http://jira.codehaus.org/browse/MENFORCER-63 Project: Maven 2.x Enforcer Plugin Issue Type: New Feature Report

[jira] Created: (MENFORCER-64) Fail the build if children in a reactor don't declare a parent

Fail the build if children in a reactor don't declare a parent -- Key: MENFORCER-64 URL: http://jira.codehaus.org/browse/MENFORCER-64 Project: Maven 2.x Enforcer Plugin Issue Type:

[jira] Created: (MENFORCER-65) Fail the build if children declare dependency versions

Fail the build if children declare dependency versions -- Key: MENFORCER-65 URL: http://jira.codehaus.org/browse/MENFORCER-65 Project: Maven 2.x Enforcer Plugin Issue Type: New Feature

[jira] Commented: (MENFORCER-64) Fail the build if children in a reactor don't declare a parent

[ http://jira.codehaus.org/browse/MENFORCER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166757#action_166757 ] Dan Fabulich commented on MENFORCER-64: --- I'd pay that price of "consistency." In the project

[jira] Commented: (MENFORCER-65) Fail the build if children declare dependency versions

[ http://jira.codehaus.org/browse/MENFORCER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166815#action_166815 ] Dan Fabulich commented on MENFORCER-65: --- What you described, "if the parent has a version, do

[jira] Created: (MNG-4100) Add maven-help-plugin to super pom

Add maven-help-plugin to super pom -- Key: MNG-4100 URL: http://jira.codehaus.org/browse/MNG-4100 Project: Maven 2 Issue Type: Improvement Affects Versions: 2.1.1 Reporter: Dan Fabulich A num

[jira] Closed: (MNG-4100) Add maven-help-plugin to super pom

[ http://jira.codehaus.org/browse/MNG-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed MNG-4100. - Resolution: Won't Fix ok, you've convinced me. (for the record I tried -cpu instead of -U, which may have been

[jira] Commented: (MNG-2576) Make Like Reactor Mode

[ http://jira.codehaus.org/browse/MNG-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176805#action_176805 ] Dan Fabulich commented on MNG-2576: --- It's not "-r" you want. -r is when you have a directory full of

[jira] Commented: (MNG-2576) Make Like Reactor Mode

[ http://jira.codehaus.org/browse/MNG-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176980#action_176980 ] Dan Fabulich commented on MNG-2576: --- Joerg, A "," is not a "/". "foo,bar" is for directory structur

[jira] Created: (MECLIPSE-122) Eclipse plugin doesn't use dependency conflict resolution mechanism

Eclipse plugin doesn't use dependency conflict resolution mechanism --- Key: MECLIPSE-122 URL: http://jira.codehaus.org/browse/MECLIPSE-122 Project: Maven 2.x Eclipse Plugin Type: Bug Versions: 2.2

[jira] Commented: (MNG-2369) Generic 3rd Party DotNet Libraries not appropriately handled

[ http://jira.codehaus.org/browse/MNG-2369?page=comments#action_74132 ] Dan Fabulich commented on MNG-2369: --- I would also direct your attention to this doc: http://docs.codehaus.org/display/MAVENUSER/BEA+Maven+Requirement+Documents > Generic 3

[jira] Created: (MNG-2560) (patch) no useful error message when M2_HOME is misconfigured during bootstrap

(patch) no useful error message when M2_HOME is misconfigured during bootstrap -- Key: MNG-2560 URL: http://jira.codehaus.org/browse/MNG-2560 Project: Maven 2 Issue

[jira] Commented: (MNG-2585) Overriding default naming

[ http://jira.codehaus.org/browse/MNG-2585?page=comments#action_76460 ] Dan Fabulich commented on MNG-2585: --- This applies not just to .NET libraries, but to all Windows DLLs, in fact. The correct solution, I believe, is to make the default rep

[jira] Commented: (MNG-2560) (patch) no useful error message when M2_HOME is misconfigured during bootstrap

[ http://jira.codehaus.org/browse/MNG-2560?page=comments#action_76485 ] Dan Fabulich commented on MNG-2560: --- I've only used it on trunk... I can try it on the -2.0.x branch today. (I think the bootstrap doesn't work on the 2.0.4 tag because th

[jira] Updated: (MNG-2560) (patch) no useful error message when M2_HOME is misconfigured during bootstrap

[ http://jira.codehaus.org/browse/MNG-2560?page=all ] Dan Fabulich updated MNG-2560: -- Attachment: 2.0.x-patch.txt Here's a second patch that works on the 2.0.x branch. > (patch) no useful error message when M2_HOME is misconfigured during bootstrap > -

[jira] Created: (SUREFIRE-375) No tests are run with TestNG 5.0 or 5.0.1

No tests are run with TestNG 5.0 or 5.0.1 - Key: SUREFIRE-375 URL: http://jira.codehaus.org/browse/SUREFIRE-375 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects

[jira] Created: (SUREFIRE-377) When JUnit and TestNG tests are in same project, only one set gets run

When JUnit and TestNG tests are in same project, only one set gets run -- Key: SUREFIRE-377 URL: http://jira.codehaus.org/browse/SUREFIRE-377 Project: Maven Surefire Issue T

[jira] Created: (SUREFIRE-376) TestNG @AfterSuite failures are ignored

TestNG @AfterSuite failures are ignored --- Key: SUREFIRE-376 URL: http://jira.codehaus.org/browse/SUREFIRE-376 Project: Maven Surefire Issue Type: Bug Reporter: Dan Fabulich Attachmen

[jira] Closed: (SUREFIRE-345) TestNG test fail with IllegalARgumentExceptoin

[ http://jira.codehaus.org/browse/SUREFIRE-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-345. - Resolution: Duplicate Dupe of SUREFIRE-316, fixed in revision 594580 > TestNG test fail with Illegal

[jira] Updated: (SUREFIRE-94) Implement getTestCount for TestNG

[ http://jira.codehaus.org/browse/SUREFIRE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-94: - Priority: Minor (was: Major) > Implement getTestCount for TestNG > -

[jira] Closed: (SUREFIRE-287) Regression: org.testng.xml.Praser#parse() signature changed

[ http://jira.codehaus.org/browse/SUREFIRE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-287. - Resolution: Fixed TestNG 5.5 and up work in latest trunk. > Regression: org.testng.xml.Praser#parse(

[jira] Closed: (SUREFIRE-168) TestNG @BeforeMethod annotations not being processed

[ http://jira.codehaus.org/browse/SUREFIRE-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-168. - Resolution: Cannot Reproduce This was probably a real bug at some point, but doesn't appear to be hap

[jira] Updated: (SUREFIRE-370) Make testing frameworks artifact names configurable in plugin

[ http://jira.codehaus.org/browse/SUREFIRE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-370: -- Priority: Minor (was: Critical) JUnit 4.4 (including -dep) is officially supported in the latest t

[jira] Created: (SUREFIRE-378) junit-dep 4.4 isn't detected; tests are treated as POJO tests.

junit-dep 4.4 isn't detected; tests are treated as POJO tests. -- Key: SUREFIRE-378 URL: http://jira.codehaus.org/browse/SUREFIRE-378 Project: Maven Surefire Issue Type: Bug

[jira] Closed: (SUREFIRE-177) Groups stipulated in the pom file get ignored when using a suiteXMLFile

[ http://jira.codehaus.org/browse/SUREFIRE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-177. - Resolution: Won't Fix This is by design; we can't contradict or override the settings in a suite XML

[jira] Updated: (SUREFIRE-92) Fix classloader separation of Test NG

[ http://jira.codehaus.org/browse/SUREFIRE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-92: - Priority: Minor (was: Major) I think this issue is minor; so long as you can fork TestNG and so long

[jira] Updated: (SUREFIRE-376) TestNG @AfterSuite failures are ignored

[ http://jira.codehaus.org/browse/SUREFIRE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-376: -- Fix Version/s: 2.4 > TestNG @AfterSuite failures are ignored >

[jira] Updated: (SUREFIRE-377) When JUnit and TestNG tests are in same project, only one set gets run

[ http://jira.codehaus.org/browse/SUREFIRE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-377: -- Fix Version/s: 2.4 > When JUnit and TestNG tests are in same project, only one set gets run > -

[jira] Updated: (SUREFIRE-375) No tests are run with TestNG 5.0 or 5.0.1

[ http://jira.codehaus.org/browse/SUREFIRE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-375: -- Fix Version/s: 2.x > No tests are run with TestNG 5.0 or 5.0.1 > --

[jira] Updated: (SUREFIRE-378) junit-dep 4.4 isn't detected; tests are treated as POJO tests.

[ http://jira.codehaus.org/browse/SUREFIRE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-378: -- Fix Version/s: 2.4 > junit-dep 4.4 isn't detected; tests are treated as POJO tests. > -

[jira] Closed: (SUREFIRE-169) No tests detected when both TestNG and JUnit in classpath

[ http://jira.codehaus.org/browse/SUREFIRE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-169. - Resolution: Duplicate It's by design that if TestNG and JUnit are both on the classpath, we want to

[jira] Closed: (SUREFIRE-165) TestNG JDK1.4 JavaDoc annotated classes never run ... and now I know why.

[ http://jira.codehaus.org/browse/SUREFIRE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-165. - Resolution: Fixed Yup, this is fixed in 2.4-SNAPSHOT trunk (at some point) > TestNG JDK1.4 JavaDoc a

[jira] Created: (SUREFIRE-379) When an exception occurs in @BeforeMethod, the exception is not recorded.

When an exception occurs in @BeforeMethod, the exception is not recorded. - Key: SUREFIRE-379 URL: http://jira.codehaus.org/browse/SUREFIRE-379 Project: Maven Surefire I

[jira] Commented: (SUREFIRE-379) When an exception occurs in @BeforeMethod, the exception is not recorded.

[ http://jira.codehaus.org/browse/SUREFIRE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114373 ] Dan Fabulich commented on SUREFIRE-379: --- Same appears to be true of @BeforeMethod and @BeforeSuite > When an excepti

[jira] Closed: (SUREFIRE-157) Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest method

[ http://jira.codehaus.org/browse/SUREFIRE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-157. - Resolution: Cannot Reproduce This must have been fixed at some point in 2.4-SNAPSHOT, because it does

[jira] Closed: (SUREFIRE-337) Regression: NoSuchMethodException: org.apache.maven.surefire.testng.TestNGXmlTestSuite.(java.io.File, java.lang.String)

[ http://jira.codehaus.org/browse/SUREFIRE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-337. - Resolution: Cannot Reproduce Seems to work now; I assume someone fixed this at some point > Regressi

[jira] Closed: (SUREFIRE-328) java.lang.NoClassDefFoundError: org/apache/maven/surefire/util/NestedRuntimeException

[ http://jira.codehaus.org/browse/SUREFIRE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-328. - Resolution: Incomplete The 2.4-SNAPSHOT integration tests are passing right now with various versions

[jira] Closed: (SUREFIRE-362) SurefireBooter does not recognise the Properties sent by SurefirePlugin

[ http://jira.codehaus.org/browse/SUREFIRE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-362. - Resolution: Fixed Fixed at some point in 2.4-SNAPSHOT trunk > SurefireBooter does not recognise the

[jira] Updated: (SUREFIRE-361) The maven-surefire-plugin fails with an NPE in TestNG 4.7

[ http://jira.codehaus.org/browse/SUREFIRE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-361: -- Summary: The maven-surefire-plugin fails with an NPE in TestNG 4.7 (was: The maven-surefire-plugin

[jira] Closed: (SUREFIRE-161) Result message of Surefire TestNG run with invalid not logical.

[ http://jira.codehaus.org/browse/SUREFIRE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-161. - Resolution: Fixed Fixed at some point in 2.4-SNAPSHOT trunk. Now the error says "SurefireExecutionE

[jira] Closed: (SUREFIRE-119) With testng, incorrect test numbers are reported if setup method throws exception.

[ http://jira.codehaus.org/browse/SUREFIRE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-119. - Resolution: Cannot Reproduce Fixed at some point in 2.4-SNAPSHOT trunk > With testng, incorrect test

[jira] Closed: (SUREFIRE-370) Make testing frameworks artifact names configurable in plugin

[ http://jira.codehaus.org/browse/SUREFIRE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-370. - Resolution: Duplicate Duplicate of SUREFIRE-352. That bug gives a slightly better justification for

[jira] Commented: (SUREFIRE-352) Get rid of hardcoded TestNG dependency name.

[ http://jira.codehaus.org/browse/SUREFIRE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114382 ] Dan Fabulich commented on SUREFIRE-352: --- Duplicated by SUREFIRE-370. There it was noted that you might also want to

[jira] Closed: (SUREFIRE-307) Tests fail if in path with spaces

[ http://jira.codehaus.org/browse/SUREFIRE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-307. - Resolution: Cannot Reproduce Can't reproduce with latest 2.4-SNAPSHOT trunk; integration test added

[jira] Closed: (SUREFIRE-342) Tests fail if JAVA_HOME path contains spaces

[ http://jira.codehaus.org/browse/SUREFIRE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-342. - Resolution: Cannot Reproduce Can't reproduce with the latest 2.4-SNAPSHOT trunk > Tests fail if JAVA

[jira] Closed: (SUREFIRE-139) JUnit 4 integration

[ http://jira.codehaus.org/browse/SUREFIRE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-139. - Resolution: Fixed JUnit 4 works fine in 2.4-SNAPSHOT trunk > JUnit 4 integration > -

[jira] Updated: (SUREFIRE-379) When an exception occurs in @BeforeMethod, the exception is not recorded.

[ http://jira.codehaus.org/browse/SUREFIRE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-379: -- Fix Version/s: 2.4 > When an exception occurs in @BeforeMethod, the exception is not recorded. > --

[jira] Closed: (SUREFIRE-364) 2.4-SNAPSHOT of 27th Oct 2007 has invalid Plexus dependency

[ http://jira.codehaus.org/browse/SUREFIRE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-364. - Resolution: Fixed > 2.4-SNAPSHOT of 27th Oct 2007 has invalid Plexus dependency > ---

[jira] Closed: (SUREFIRE-361) The maven-surefire-plugin fails with an NPE in TestNG 4.7

[ http://jira.codehaus.org/browse/SUREFIRE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-361. - Resolution: Fixed Fixed in revision 596894 > The maven-surefire-plugin fails with an NPE in TestNG 4

[jira] Created: (SUREFIRE-380) TestNG 5.2 not recognized

TestNG 5.2 not recognized - Key: SUREFIRE-380 URL: http://jira.codehaus.org/browse/SUREFIRE-380 Project: Maven Surefire Issue Type: Bug Components: TestNG support Reporter: Dan Fabulich Downloa

[jira] Closed: (SUREFIRE-380) TestNG 5.2 not recognized

[ http://jira.codehaus.org/browse/SUREFIRE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-380. - Resolution: Fixed Fix Version/s: 2.4 fixed in revision 596898 > TestNG 5.2 not recognized > -

[jira] Closed: (SUREFIRE-59) Not compatible with TestNG 5.2: java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V

[ http://jira.codehaus.org/browse/SUREFIRE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-59. Resolution: Fixed TestNG 5.2 works in the latest 2.4-SNAPSHOT in trunk, but you'll probably prefer to u

[jira] Closed: (SUREFIRE-58) Not compatible with TestNG 5.4: InstantiationException: org.testng.internal.annotations.JDK15AnnotationFinder

[ http://jira.codehaus.org/browse/SUREFIRE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-58. Resolution: Cannot Reproduce The current latest 2.4-SNAPSHOT trunk works for me with TestNG 5.1, 5.2, 5.

[jira] Updated: (SUREFIRE-376) TestNG @AfterSuite failures are ignored

[ http://jira.codehaus.org/browse/SUREFIRE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-376: -- Component/s: TestNG support > TestNG @AfterSuite failures are ignored > ---

[jira] Updated: (SUREFIRE-92) Fix classloader separation of Test NG

[ http://jira.codehaus.org/browse/SUREFIRE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-92: - Component/s: TestNG support > Fix classloader separation of Test NG >

[jira] Updated: (SUREFIRE-94) Implement getTestCount for TestNG

[ http://jira.codehaus.org/browse/SUREFIRE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-94: - Component/s: TestNG support > Implement getTestCount for TestNG > - >

[jira] Commented: (SUREFIRE-90) Add Distributed testing ability

[ http://jira.codehaus.org/browse/SUREFIRE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114397 ] Dan Fabulich commented on SUREFIRE-90: -- Users can already configure TestNG to do whatever they want using suite files.

[jira] Closed: (SUREFIRE-363) The maven-surefire-plugin fails with a NoSuchMethodException.

[ http://jira.codehaus.org/browse/SUREFIRE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-363. - Resolution: Cannot Reproduce I unpacked that project and ran "mvn test"; I got 1 test suceeded. I gu

[jira] Updated: (SUREFIRE-375) No tests are run with TestNG 5.0 or 5.0.1

[ http://jira.codehaus.org/browse/SUREFIRE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-375: -- Priority: Minor (was: Major) In my opinion, this issue is minor, because it's just one obsolete ve

[jira] Closed: (SUREFIRE-112) StringIndexOutOfBoundsException building reports from TestNG tests

[ http://jira.codehaus.org/browse/SUREFIRE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-112. - Resolution: Cannot Reproduce Can't reproduce in the latest 2.4-SNAPSHOT trunk. Must have gotten fixe

[jira] Closed: (SUREFIRE-366) Out Of Memory exceptions in 2.4 SNAPSHOTs

[ http://jira.codehaus.org/browse/SUREFIRE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-366. - Resolution: Cannot Reproduce Some very large projects are running successfully with 2.4-SNAPSHOT. Pl

[jira] Created: (SUREFIRE-381) TestNG Reporter.log() calls don't show up in any reports

TestNG Reporter.log() calls don't show up in any reports Key: SUREFIRE-381 URL: http://jira.codehaus.org/browse/SUREFIRE-381 Project: Maven Surefire Issue Type: Bug Component

[jira] Updated: (SUREFIRE-381) TestNG Reporter.log() calls don't show up in any reports

[ http://jira.codehaus.org/browse/SUREFIRE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-381: -- Attachment: testng-reporter.zip example project that uses the reporter > TestNG Reporter.log() cal

[jira] Created: (SUREFIRE-382) TestNG parameterized test failures don't specify parameterized values

TestNG parameterized test failures don't specify parameterized values - Key: SUREFIRE-382 URL: http://jira.codehaus.org/browse/SUREFIRE-382 Project: Maven Surefire Issue Typ

[jira] Created: (SUREFIRE-383) Expose TestNG support for re-running failed tests

Expose TestNG support for re-running failed tests - Key: SUREFIRE-383 URL: http://jira.codehaus.org/browse/SUREFIRE-383 Project: Maven Surefire Issue Type: New Feature Components: Tes

[jira] Created: (SUREFIRE-384) Allow TestNG to generate its native XML output

Allow TestNG to generate its native XML output -- Key: SUREFIRE-384 URL: http://jira.codehaus.org/browse/SUREFIRE-384 Project: Maven Surefire Issue Type: Improvement Components: TestNG su

[jira] Updated: (SUREFIRE-381) TestNG Reporter.log() calls don't show up in any reports

[ http://jira.codehaus.org/browse/SUREFIRE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-381: -- Fix Version/s: 2.4 > TestNG Reporter.log() calls don't show up in any reports > ---

[jira] Updated: (SUREFIRE-384) Allow TestNG to generate its native XML output

[ http://jira.codehaus.org/browse/SUREFIRE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-384: -- Fix Version/s: 2.4 > Allow TestNG to generate its native XML output > -

[jira] Updated: (SUREFIRE-382) TestNG parameterized test failures don't specify parameterized values

[ http://jira.codehaus.org/browse/SUREFIRE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-382: -- Fix Version/s: 2.4 > TestNG parameterized test failures don't specify parameterized values > --

[jira] Updated: (SUREFIRE-383) Expose TestNG support for re-running failed tests

[ http://jira.codehaus.org/browse/SUREFIRE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-383: -- Fix Version/s: 2.4 > Expose TestNG support for re-running failed tests > --

[jira] Commented: (SUREFIRE-376) TestNG @AfterSuite failures are ignored

[ http://jira.codehaus.org/browse/SUREFIRE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114406 ] Dan Fabulich commented on SUREFIRE-376: --- JUnit 4 handles @AfterClass failures as separate pseudo-testCases. As a re

[jira] Commented: (SUREFIRE-376) TestNG @AfterSuite failures are ignored

[ http://jira.codehaus.org/browse/SUREFIRE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114407 ] Dan Fabulich commented on SUREFIRE-376: --- One (better?) way to handle this would be to resolve SUREFIRE-384 and consum

[jira] Updated: (SUREFIRE-379) When an exception occurs in @BeforeMethod, the exception is not recorded.

[ http://jira.codehaus.org/browse/SUREFIRE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-379: -- One good way to handle this might be to fix SUREFIRE-384 and let the reports consume TestNG's native X

[jira] Updated: (SUREFIRE-379) When an exception occurs in @BeforeMethod, the exception is not recorded.

[ http://jira.codehaus.org/browse/SUREFIRE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-379: -- Priority: Critical (was: Major) > When an exception occurs in @BeforeMethod, the exception is not

[jira] Updated: (SUREFIRE-376) TestNG @AfterSuite failures are ignored

[ http://jira.codehaus.org/browse/SUREFIRE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-376: -- Priority: Critical (was: Major) > TestNG @AfterSuite failures are ignored > --

[jira] Created: (SUREFIRE-385) Booter can't decode properties when contains commas

Booter can't decode properties when contains commas Key: SUREFIRE-385 URL: http://jira.codehaus.org/browse/SUREFIRE-385 Project: Maven Surefire Issue Type: Bug Component

[jira] Closed: (SUREFIRE-385) Booter can't decode properties when contains commas

[ http://jira.codehaus.org/browse/SUREFIRE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-385. - Resolution: Fixed Fix Version/s: 2.4 Fixed in revision 597008 > Booter can't decode propertie

[jira] Closed: (SUREFIRE-325) when parsing excludedGroups config prop, trim leading and trailing whitespace off of group names

[ http://jira.codehaus.org/browse/SUREFIRE-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-325. - Resolution: Fixed This was fixed a while back by just passing the string along to TestNG as a config

[jira] Closed: (SUREFIRE-384) Allow TestNG to generate its native XML output

[ http://jira.codehaus.org/browse/SUREFIRE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-384. - Resolution: Fixed fixed in revision 597190 > Allow TestNG to generate its native XML output > --

[jira] Closed: (SUREFIRE-378) junit-dep 4.4 isn't detected; tests are treated as POJO tests.

[ http://jira.codehaus.org/browse/SUREFIRE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-378. - Resolution: Fixed fixed in revision 597192 > junit-dep 4.4 isn't detected; tests are treated as POJO

[jira] Created: (SUREFIRE-386) TestNG native XML is generated even if you specify disableXmlReport

TestNG native XML is generated even if you specify disableXmlReport --- Key: SUREFIRE-386 URL: http://jira.codehaus.org/browse/SUREFIRE-386 Project: Maven Surefire Issue Type: B

[jira] Closed: (SUREFIRE-379) When an exception occurs in @BeforeMethod, the exception is not recorded.

[ http://jira.codehaus.org/browse/SUREFIRE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-379. - Resolution: Fixed fixed in revision 597234 > When an exception occurs in @BeforeMethod, the exceptio

[jira] Closed: (SUREFIRE-376) TestNG @AfterSuite failures are ignored

[ http://jira.codehaus.org/browse/SUREFIRE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-376. - Resolution: Fixed fixed in revision 597234 > TestNG @AfterSuite failures are ignored > -

[jira] Updated: (SUREFIRE-377) When JUnit and TestNG tests are in same project, only one set gets run

[ http://jira.codehaus.org/browse/SUREFIRE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-377: -- Fix Version/s: (was: 2.4) IMO, this problem is probably too hard to be worth solving. See the

[jira] Updated: (SUREFIRE-377) When JUnit and TestNG tests are in same project, only one set gets run

[ http://jira.codehaus.org/browse/SUREFIRE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-377: -- Attachment: surefire377.patch I'm going to revert my workspace to blow away my current work on this

[jira] Closed: (SUREFIRE-52) XML Reports include testcases from previous tests

[ http://jira.codehaus.org/browse/SUREFIRE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-52. Resolution: Cannot Reproduce This got fixed at some point. Checked in an integration test in revision

[jira] Closed: (SUREFIRE-160) Bug into xml report generation

[ http://jira.codehaus.org/browse/SUREFIRE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-160. - Resolution: Cannot Reproduce This got fixed at some point. Integration test checked in revision 5972

[jira] Closed: (SUREFIRE-103) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)

[ http://jira.codehaus.org/browse/SUREFIRE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-103. - Resolution: Incomplete Fix Version/s: (was: 2.4) This isn't enough information to work on

[jira] Closed: (SUREFIRE-44) Inner class inclusion too powerful

[ http://jira.codehaus.org/browse/SUREFIRE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-44. Resolution: Cannot Reproduce Fix Version/s: (was: 2.4) Can't reproduce; integration checked i

[jira] Closed: (SUREFIRE-266) Exception if a test case is in the default package

[ http://jira.codehaus.org/browse/SUREFIRE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-266. - Resolution: Cannot Reproduce Fix Version/s: (was: 2.4) Must have been fixed at some point;

[jira] Closed: (SUREFIRE-355) Sort tests in alphabetical order in the report

[ http://jira.codehaus.org/browse/SUREFIRE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-355. - Resolution: Duplicate Fix Version/s: (was: 2.x) Duplicate of SUREFIRE-321 > Sort tests in

  1   2   3   4   5   6   >