[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11

[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291598#comment-291598 ] Deivydas edited comment on SUREFIRE-827 at 2/14/12 3:19 AM: We have

[jira] (MSITE-631) Make site:attach-descriptor goal @threadSafe

Andreas Sewe created MSITE-631: -- Summary: Make site:attach-descriptor goal @threadSafe Key: MSITE-631 URL: https://jira.codehaus.org/browse/MSITE-631 Project: Maven 2.x and 3.x Site Plugin

[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11

[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291598#comment-291598 ] Deivydas edited comment on SUREFIRE-827 at 2/14/12 3:18 AM: We have

[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11

[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291598#comment-291598 ] Deivydas commented on SUREFIRE-827: --- We have the same issue (-Dtest=test1,test2 doesn't run any

[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11

[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291598#comment-291598 ] Deivydas edited comment on SUREFIRE-827 at 2/14/12 3:17 AM: We have

[jira] (MECLIPSE-713) Please release 2.9

[ https://jira.codehaus.org/browse/MECLIPSE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291600#comment-291600 ] Heiko Maaß edited comment on MECLIPSE-713 at 2/14/12 4:09 AM: -- +1

[jira] (MECLIPSE-713) Please release 2.9

[ https://jira.codehaus.org/browse/MECLIPSE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291600#comment-291600 ] Heiko Maaß commented on MECLIPSE-713: - +1 from me. Please release 2.9. By the way: No

[jira] (SUREFIRE-825) NPE in JUnit4TestChecker if org.junit.runner.RunWith class can't be loaded by testClassloader

[ https://jira.codehaus.org/browse/SUREFIRE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291613#comment-291613 ] Kristian Rosenvold commented on SUREFIRE-825: - A test would be *really* nice

[jira] (SUREFIRE-825) NPE in JUnit4TestChecker if org.junit.runner.RunWith class can't be loaded by testClassloader

[ https://jira.codehaus.org/browse/SUREFIRE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291613#comment-291613 ] Kristian Rosenvold edited comment on SUREFIRE-825 at 2/14/12 6:17 AM:

[jira] (MCOMPILER-165) Child modules don't seem to be able to use a different compilerId to their parent modules when built from the parent POM.

Edd grant created MCOMPILER-165: --- Summary: Child modules don't seem to be able to use a different compilerId to their parent modules when built from the parent POM. Key: MCOMPILER-165 URL:

[jira] (MNG-5244) Cleaner way to support different languages

Martin Eisengardt created MNG-5244: -- Summary: Cleaner way to support different languages Key: MNG-5244 URL: https://jira.codehaus.org/browse/MNG-5244 Project: Maven 2 3 Issue Type:

[jira] (SUREFIRE-825) NPE in JUnit4TestChecker if org.junit.runner.RunWith class can't be loaded by testClassloader

[ https://jira.codehaus.org/browse/SUREFIRE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291637#comment-291637 ] Jan Sievers commented on SUREFIRE-825: -- I will add a test to the patch NPE

[jira] (MCOMPILER-165) Child modules don't seem to be able to use a different compilerId to their parent modules when built from the parent POM.

[ https://jira.codehaus.org/browse/MCOMPILER-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291640#comment-291640 ] Edd grant commented on MCOMPILER-165: - Have just done some testing and have discovered that

[jira] (MRELEASE-638) release:prepare fails w/ java.lang.ClassFormatError: Invalid pc in LineNumberTable in class file org/apache/commons/lang/StringUtils

[ https://jira.codehaus.org/browse/MRELEASE-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-638. --- Resolution: Fixed Fix Version/s: 2.3 Assignee: Robert Scholte Fixed in [rev.

[jira] (SUREFIRE-835) Tests for maven plugins are incompatible with maven 3.0.4

[ https://jira.codehaus.org/browse/SUREFIRE-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291645#comment-291645 ] Olivier Lamy commented on SUREFIRE-835: --- with maven3 you must use {code:xml}

[jira] (MNG-5245) upgrade default plugins versions

Olivier Lamy created MNG-5245: - Summary: upgrade default plugins versions Key: MNG-5245 URL: https://jira.codehaus.org/browse/MNG-5245 Project: Maven 2 3 Issue Type: Improvement

[jira] (MNG-5245) upgrade default plugins versions

[ https://jira.codehaus.org/browse/MNG-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-5245: -- Fix Version/s: 3.0.5 upgrade default plugins versions

[jira] (MNG-5245) upgrade default plugins versions

[ https://jira.codehaus.org/browse/MNG-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291647#comment-291647 ] Olivier Lamy commented on MNG-5245: --- surefire 2.12 r1244153 upgrade default

[jira] (MRELEASE-320) Expressions are replaced with settings.xml values during release:prepare

[ https://jira.codehaus.org/browse/MRELEASE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-320. --- Resolution: Not A Bug Assignee: Robert Scholte This is intended. It must be possible for

[jira] (MRELEASE-539) prepare-with-pom fails for git provider

[ https://jira.codehaus.org/browse/MRELEASE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-539: Component/s: (was: prepare) prepare-with-pom Git

[jira] (MRELEASE-304) Wrong version in development pom.xml

[ https://jira.codehaus.org/browse/MRELEASE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-304. --- Resolution: Incomplete Assignee: Robert Scholte Seems to be fixed in [rev.

[jira] (MRELEASE-642) prepare tags the wrong source

[ https://jira.codehaus.org/browse/MRELEASE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-642: Component/s: (was: prepare) prepare-with-pom prepare tags the wrong

[jira] (MRAR-22) Allow filtering of source resources

[ https://jira.codehaus.org/browse/MRAR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291657#comment-291657 ] Carsten Erker commented on MRAR-22: --- Today I fixed this. I have to write some tests and will provide

[jira] (SUREFIRE-835) Tests for maven plugins are incompatible with maven 3.0.4

[ https://jira.codehaus.org/browse/SUREFIRE-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-835. --- Resolution: Duplicate Assignee: Kristian Rosenvold This issue is basically a

[jira] (MRELEASE-674) release plugin converts explicit version to snapshot

[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-674: Component/s: (was: prepare) update-versions release plugin converts

[jira] (MRELEASE-701) maven:prepare failed with GIT SCM in multimodule project with quite same name

[ https://jira.codehaus.org/browse/MRELEASE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-701: Component/s: Git maven:prepare failed with GIT SCM in multimodule project with quite

[jira] (MRELEASE-726) mvn release:prepare-with-pom not honouring the commitByProject parameter.

[ https://jira.codehaus.org/browse/MRELEASE-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-726: Component/s: (was: prepare) prepare-with-pom Git

[jira] (MRELEASE-543) prepare-with-pom : inherited dependencies exclusion are lost in release-pom.xml

[ https://jira.codehaus.org/browse/MRELEASE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-543: Component/s: (was: prepare) prepare-with-pom prepare-with-pom :

[jira] (MRELEASE-544) prepare-with-pom : inherited plugins configuration are lost in release-pom.xml

[ https://jira.codehaus.org/browse/MRELEASE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-544: Component/s: (was: perform) prepare-with-pom prepare-with-pom :

[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11

[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291662#comment-291662 ] Kristian Rosenvold commented on SUREFIRE-827: - Francois; This is a separate issue

[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11

[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-827: Component/s: (was: Maven Surefire Plugin) Junit 4.7+ (parallel)

[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11

[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SUREFIRE-827 started by Kristian Rosenvold. Surefire 2.12 cannot run a single test, regression from 2.11

[jira] (MRELEASE-601) The Maven 2 release plugin modifies CDATA elements in pom.xml files.

[ https://jira.codehaus.org/browse/MRELEASE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-601: Component/s: prepare The Maven 2 release plugin modifies CDATA elements in pom.xml

[jira] (MRELEASE-672) branching a sub module during a build

[ https://jira.codehaus.org/browse/MRELEASE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-672: Component/s: branch Description: We have to requirement to create a reparate branch of a

[jira] (MRELEASE-598) Repeatedly prompt for same release/next development versions of snapshot dependencies in multi-module projects

[ https://jira.codehaus.org/browse/MRELEASE-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-598: Component/s: prepare Repeatedly prompt for same release/next development versions of

[jira] (MRELEASE-644) Do a pre-check for Git repositories to make sure the name and email are set

[ https://jira.codehaus.org/browse/MRELEASE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-644: Component/s: prepare Git Do a pre-check for Git repositories to make

[jira] (MRELEASE-664) [maven release plugin] release:perform wait until build completes before uploading artifacts

[ https://jira.codehaus.org/browse/MRELEASE-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-664: Component/s: perform [maven release plugin] release:perform wait until build completes

[jira] (MRELEASE-578) Changing goals during perform produce strange comportment

[ https://jira.codehaus.org/browse/MRELEASE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-578: Description: I have a Multi Module Maven project. I personalise a profil especially for

[jira] (MRELEASE-594) release:prepare should stop when there is snapshots in dependencies management

[ https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-594: Component/s: prepare release:prepare should stop when there is snapshots in dependencies

[jira] (MRELEASE-568) Release plugin (in perform phase) ignore -f directive (non-default pom.xml file)

[ https://jira.codehaus.org/browse/MRELEASE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-568. --- Resolution: Duplicate Assignee: Robert Scholte Duplicate of MRELEASE-618, is fixed for

[jira] (MRELEASE-611) The update-versions goal fails when project is not at a SNAPSHOT version

[ https://jira.codehaus.org/browse/MRELEASE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-611: Component/s: update-versions The update-versions goal fails when project is not at a

[jira] (MRELEASE-552) Add useEditMode option to release:update-versions

[ https://jira.codehaus.org/browse/MRELEASE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-552: Component/s: update-versions Add useEditMode option to release:update-versions

[jira] (MRELEASE-490) Enable promotion process

[ https://jira.codehaus.org/browse/MRELEASE-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-490: Component/s: stage Enable promotion process

[jira] (MRELEASE-623) unexpected mvn release:prepare behavior for project with version2.2-SNAPshot/version

[ https://jira.codehaus.org/browse/MRELEASE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-623: Component/s: prepare unexpected mvn release:prepare behavior for project with

[jira] (MRELEASE-581) Git relative pathing broken with release plugin

[ https://jira.codehaus.org/browse/MRELEASE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-581: Component/s: prepare Git Description: i have a multimodule project, and

[jira] (MRELEASE-728) The commit message for release:branch is wrong

[ https://jira.codehaus.org/browse/MRELEASE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-728: Component/s: Git branch The commit message for release:branch is wrong

[jira] (MRELEASE-619) release:branch doesn't work as expected with multi-module projects

[ https://jira.codehaus.org/browse/MRELEASE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-619: Component/s: branch release:branch doesn't work as expected with multi-module projects

[jira] (MRELEASE-525) Update-versions does not work in batch mode

[ https://jira.codehaus.org/browse/MRELEASE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-525: Component/s: update-versions Description: When I run the {{release:update-versions}} goal

[jira] (SUREFIRE-836) regression with surefire 2.12 plugin and SecurityManager

Henning Schmiedehausen created SUREFIRE-836: --- Summary: regression with surefire 2.12 plugin and SecurityManager Key: SUREFIRE-836 URL: https://jira.codehaus.org/browse/SUREFIRE-836 Project:

[jira] (SUREFIRE-770) persistence.xml in src/test/resources/META-INF is not taken into account

[ https://jira.codehaus.org/browse/SUREFIRE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291687#comment-291687 ] Giovanni Silva commented on SUREFIRE-770: - I have this issue to, I think is related to