[jira] Commented: (MAVENUPLOAD-1799) Upload request for swingx 0.9 for jdk 1.5

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114417 ] Wim Deblauwe commented on MAVENUPLOAD-1799: --- Just tested it now and seems to work great. I mailed the bundle

[jira] Commented: (MAVENUPLOAD-1815) upload new release 1.11 to org.mentaframework

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114415 ] Carlos Sanchez commented on MAVENUPLOAD-1815: - i would be interested in knowing why something needed for co

[jira] Commented: (MAVENUPLOAD-1819) Request for upload of org-lib-usurper-1.1.0

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114413 ] Carlos Sanchez commented on MAVENUPLOAD-1819: - no, it has to match the domain name > Request for upload of

[jira] Commented: (MAVENUPLOAD-1806) rsync request: gr.abiss

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114412 ] Carlos Sanchez commented on MAVENUPLOAD-1806: - it would, see other SF projects that are already being synce

[jira] Commented: (MAVENUPLOAD-1799) Upload request for swingx 0.9 for jdk 1.5

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114414 ] Carlos Sanchez commented on MAVENUPLOAD-1799: - looks good to me, have you tried it with your projects ? >

[jira] Closed: (MAVENUPLOAD-1822) Upload ZK Forge Libraries to the central repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1822. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload ZK Forge Libraries to the c

[jira] Closed: (MAVENUPLOAD-1814) Upload ZK Forge Libraries to the central repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1814. --- Assignee: Carlos Sanchez Resolution: Won't Fix > Upload ZK Forge Libraries to t

[jira] Issue Comment Edited: (MRM-594) add some minimal hook in LegacyPathParser to allow exception management in artifact resolution

[ http://jira.codehaus.org/browse/MRM-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114305 ] ndeloof edited comment on MRM-594 at 11/21/07 12:10 AM: This new patch covers : - make PathPars

[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] 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-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] 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] 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] 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] 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-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-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] 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] 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-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] 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-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] 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] 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] Created: (MRAR-20) Allow specification of where the jars and other files end up in the rar.

Allow specification of where the jars and other files end up in the rar. Key: MRAR-20 URL: http://jira.codehaus.org/browse/MRAR-20 Project: Maven 2.x Rar Plugin Issue T

[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-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] 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] Commented: (MRAR-3) Rar should be, or be able to be considered as, attached artifacts

[ http://jira.codehaus.org/browse/MRAR-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114395 ] David Jencks commented on MRAR-3: - I think this is still relevant. The workaround would be to build the jar in a separate proje

[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] 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-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] Commented: (MRAR-18) Permit creation of client

[ http://jira.codehaus.org/browse/MRAR-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114394 ] David Jencks commented on MRAR-18: -- Can you provide some reference for this concept of a rar client module? I have not heard

[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] 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-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] 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-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] 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] 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-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] 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-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] 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-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] 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-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] 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-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] 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-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-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] 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] Updated: (MPMD-59) Upgrade to PMD 4.0

[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MPMD-59: -- Attachment: patch.txt I've upped the version of PMD to 4.1 and removed the special cases for Jaxen and Xom, bec

[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] 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] 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] 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] 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-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-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-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] 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] 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] 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] Commented: (MPMD-59) Upgrade to PMD 4.0

[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114363 ] Nick Stolwijk commented on MPMD-59: --- Oh, and the deployed PMD 4.1 jar file is compiled with Java 5 instead of 1.4. > Upgrade

[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] 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] 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-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] Commented: (MASSEMBLY-241) Multiple includes in dependencySet

[ http://jira.codehaus.org/browse/MASSEMBLY-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114354 ] I-Ann Chen commented on MASSEMBLY-241: -- It seems to fail after the first wildcard. For example, the following would i

[jira] Updated: (MECLIPSE-172) Don't add Default ClasspathContainer if a alternate JRE or a "Execution Environment" is configured as ClasspathContainer.

[ http://jira.codehaus.org/browse/MECLIPSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-172: - Testcase included: yes > Don't add Default ClasspathContainer if a alternate JRE or a "Execut

[jira] Commented: (MPMD-59) Upgrade to PMD 4.0

[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114353 ] Nick Stolwijk commented on MPMD-59: --- PMD 4.1 has been released to central, but unfortunately without a pom file. Also, there

[jira] Commented: (SCM-351) generated client spec name fails if there is a space or tilde in directory name

[ http://jira.codehaus.org/browse/SCM-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114352 ] zak jacobson commented on SCM-351: -- Here is the output. {noformat} [DEBUG] Updating clientspec: Client: johndoe-SDGL04301175-Ma

[jira] Created: (SCM-351) generated client spec name fails if there is a space or tilde in directory name

generated client spec name fails if there is a space or tilde in directory name --- Key: SCM-351 URL: http://jira.codehaus.org/browse/SCM-351 Project: Maven SCM Issu

[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] Commented: (MPMD-59) Upgrade to PMD 4.0

[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114348 ] Travis Fielding commented on MPMD-59: - Hey Russ, I was just referring to the fact that PMD 4.1 itself has been released.

[jira] Commented: (MPMD-59) Upgrade to PMD 4.0

[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114347 ] Russ Carver commented on MPMD-59: - Great! Is this the PMD bundled with Maven? Or just PMD itself? And has this report genera

[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] Commented: (MPMD-59) Upgrade to PMD 4.0

[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114346 ] Travis Fielding commented on MPMD-59: - PMD is now at version 4.1. > Upgrade to PMD 4.0 > -- > >

[jira] Issue Comment Edited: (MRM-594) add some minimal hook in LegacyPathParser to allow exception management in artifact resolution

[ http://jira.codehaus.org/browse/MRM-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114305 ] ndeloof edited comment on MRM-594 at 11/20/07 12:32 PM: This new patch covers : - make PathPars

[jira] Created: (MRELEASE-298) -DupdateDependencies flag is not honored in non-interactive mode

-DupdateDependencies flag is not honored in non-interactive mode Key: MRELEASE-298 URL: http://jira.codehaus.org/browse/MRELEASE-298 Project: Maven 2.x Release Plugin Issue Typ

[jira] Commented: (MECLIPSE-172) Don't add Default ClasspathContainer if a alternate JRE or a "Execution Environment" is configured as ClasspathContainer.

[ http://jira.codehaus.org/browse/MECLIPSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114340 ] Nathan Beyer (Cerner) commented on MECLIPSE-172: Can someone set the "test case" and "patch available" flag

[jira] Created: (MNG-3295) Cannot use offline (-o) if a is declared

Cannot use offline (-o) if a is declared - Key: MNG-3295 URL: http://jira.codehaus.org/browse/MNG-3295 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation

[jira] Created: (MANTTASKS-100) Deploy tasks creates incorrect checksums

Deploy tasks creates incorrect checksums Key: MANTTASKS-100 URL: http://jira.codehaus.org/browse/MANTTASKS-100 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: deploy task Affect

[jira] Created: (MANTTASKS-99) Create a nightly snapshot build on a CI server

Create a nightly snapshot build on a CI server -- Key: MANTTASKS-99 URL: http://jira.codehaus.org/browse/MANTTASKS-99 Project: Maven 2.x Ant Tasks Issue Type: Task Affects Versions: 2.0.7

[jira] Commented: (MRELEASE-295) Internal dependencies left at old snapshot

[ http://jira.codehaus.org/browse/MRELEASE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114322 ] Stan Klimoff commented on MRELEASE-295: --- Observed this behavior in versions beta-4 through beta-7. Projects using de

[jira] Closed: (MNG-3294) [file-management] Add a parameter to throw or not IOException in delete( FileSet fileSet )

[ http://jira.codehaus.org/browse/MNG-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3294. Assignee: Vincent Siveton Resolution: Fixed done in r596648 > [file-management] Add a parameter to

[jira] Created: (MNG-3294) [file-management] Add a parameter to throw or not IOException in delete( FileSet fileSet )

[file-management] Add a parameter to throw or not IOException in delete( FileSet fileSet ) -- Key: MNG-3294 URL: http://jira.codehaus.org/browse/MNG-3294 Project:

[jira] Created: (MECLIPSE-347) Compile Fail

Compile Fail Key: MECLIPSE-347 URL: http://jira.codehaus.org/browse/MECLIPSE-347 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Reporter: Margarita Buriano I created a simple project with new maven project optio

[jira] Commented: (MRM-599) maven-metadata.xml is not part of defined whitelist (skipping transfer).

[ http://jira.codehaus.org/browse/MRM-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114316 ] Mathias Arens commented on MRM-599: --- Here is a list of the repositories I have configured. If I have the first four repositor

[jira] Commented: (MRM-599) maven-metadata.xml is not part of defined whitelist (skipping transfer).

[ http://jira.codehaus.org/browse/MRM-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114308 ] Mathias Arens commented on MRM-599: --- I just noticed that this error occurs only if you have more than 4 (>4) repositories/pro

[jira] Closed: (MRM-596) regression : cannot get java-sources anymore from maven1

[ http://jira.codehaus.org/browse/MRM-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-596. Resolution: Fixed Patch applied (-r596620). Thanks Nicolas! :) > regression : cannot get java-sources any

[jira] Created: (MRM-599) maven-metadata.xml is not part of defined whitelist (skipping transfer).

maven-metadata.xml is not part of defined whitelist (skipping transfer). Key: MRM-599 URL: http://jira.codehaus.org/browse/MRM-599 Project: Archiva Issue Type: Bug

[jira] Created: (MNG-3293) Activating more than one profile with the same build plugin results in only one execution

Activating more than one profile with the same build plugin results in only one execution - Key: MNG-3293 URL: http://jira.codehaus.org/browse/MNG-3293 Project: M

[jira] Updated: (MRM-594) add some minimal hook in LegacyPathParser to allow exception management in artifact resolution

[ http://jira.codehaus.org/browse/MRM-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof updated MRM-594: Attachment: MRM-594-with-web-ui.patch This new patch covers : - make PathParsers plexus component instead o

[jira] Updated: (MECLIPSE-344) connecting existing workspace artifact-projects

[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven updated MECLIPSE-344: -- Attachment: workspace_with_limit.patch There are a few jira's about exludin

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114300 ] Venelin Mitov commented on MSITE-129: - I would be also very interested in having this issue fixed. In the organization wh

[jira] Created: (CONTINUUM-1573) not able to download files from working directory in any format other than html

not able to download files from working directory in any format other than html --- Key: CONTINUUM-1573 URL: http://jira.codehaus.org/browse/CONTINUUM-1573 Project: Continuum

[jira] Closed: (MRM-598) Validation error on new repository creation

[ http://jira.codehaus.org/browse/MRM-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-598. Resolution: Cannot Reproduce > Validation error on new repository creation > ---

  1   2   >