[jira] (MASSEMBLY-578) lineEnding parameter makes assembly ignore empty directories

[ https://jira.codehaus.org/browse/MASSEMBLY-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292972#comment-292972 ] Ed Hillmann edited comment on MASSEMBLY-578 at 2/28/12 11:38 PM: -

[jira] (MASSEMBLY-578) lineEnding parameter makes assembly ignore empty directories

[ https://jira.codehaus.org/browse/MASSEMBLY-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292972#comment-292972 ] Ed Hillmann commented on MASSEMBLY-578: --- I can confirm this occurs when using a type of "d

[jira] (SUREFIRE-745) -Dtest supports multiple test classes but not multiple test methods

[ https://jira.codehaus.org/browse/SUREFIRE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292966#comment-292966 ] rainLee commented on SUREFIRE-745: -- my pleasure:-) > -Dtest supports multiple t

[jira] (MASSEMBLY-601) http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html seems to have the components of a filter element in the wrong order

Benson Margulies created MASSEMBLY-601: -- Summary: http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html seems to have the components of a filter element in the wrong order Key: MASSEMBLY-601 UR

[jira] (MNG-5255) Dependency with 'provided' scope has its transitive dependency included in final artifact

Bart Skondin created MNG-5255: - Summary: Dependency with 'provided' scope has its transitive dependency included in final artifact Key: MNG-5255 URL: https://jira.codehaus.org/browse/MNG-5255 Project: Mav

[jira] (MRRESOURCES-58) 'process' goal fails with NPE at the root of a reactor if child modules use version ranges for dependencies

[ https://jira.codehaus.org/browse/MRRESOURCES-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ivanov updated MRRESOURCES-58: - Attachment: version-ranges-bugfix-v2.patch Actually, on the second thought, filtering is o

[jira] (ARCHETYPE-401) use repo.maven.apache.org CNAME to provide more stability

[ https://jira.codehaus.org/browse/ARCHETYPE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated ARCHETYPE-401: Summary: use repo.maven.apache.org CNAME to provide more stability (was: use repo.maven.apac

[jira] (ARCHETYPE-401) use repo.maven.apache.org CNAME or repo to provide more stability

[ https://jira.codehaus.org/browse/ARCHETYPE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed ARCHETYPE-401. --- Resolution: Fixed Fix Version/s: 2.3 Assignee: Herve Boutemy done in [r1294863|

[jira] (ARCHETYPE-401) use repo.maven.apache.org CNAME or repo to provide more stability

Herve Boutemy created ARCHETYPE-401: --- Summary: use repo.maven.apache.org CNAME or repo to provide more stability Key: ARCHETYPE-401 URL: https://jira.codehaus.org/browse/ARCHETYPE-401 Project: Maven

[jira] (MRELEASE-663) Null error when project is too close to root

[ https://jira.codehaus.org/browse/MRELEASE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292955#comment-292955 ] Robert Scholte commented on MRELEASE-663: - Could you specify the version of the maven-rel

[jira] (MRELEASE-265) Make pom writable on prepare

[ https://jira.codehaus.org/browse/MRELEASE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292953#comment-292953 ] Robert Scholte commented on MRELEASE-265: - Why is the POM readonly? > Ma

[jira] (MRELEASE-634) Versions of snapshot dependencies to the same artifact with different classifiers are not updated correctly during release:prepare

[ https://jira.codehaus.org/browse/MRELEASE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-634. --- Resolution: Duplicate Duplicate of MRELEASE-161 > Versions of snapshot dependen

[jira] (MDEPLOY-147) deploy snapshot without timestamp

[ https://jira.codehaus.org/browse/MDEPLOY-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDEPLOY-147. -- Resolution: Not A Bug See the [Combatibility Notes| https://cwiki.apache.org/MAVEN/maven-3x-compat

[jira] (MRELEASE-400) Failed to validate POM for project ... at ...\release-pom.xml

[ https://jira.codehaus.org/browse/MRELEASE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-400: Description: When releasing the multimodule project and one of the transitive dependencies is

[jira] (MRELEASE-400) Failed to validate POM for project ... at ...\release-pom.xml

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

[jira] (MWAR-277) New version does not work with yuicompressor-maven-plugin. v2.0.2 works.

Eric Miller created MWAR-277: Summary: New version does not work with yuicompressor-maven-plugin. v2.0.2 works. Key: MWAR-277 URL: https://jira.codehaus.org/browse/MWAR-277 Project: Maven 2.x WAR Plugin

[jira] (MRELEASE-287) release:prepare does not change the version of parent snapshot

[ https://jira.codehaus.org/browse/MRELEASE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-287. --- Resolution: Duplicate Duplicate of MRELEASE-317, which was already fixed with version 2.1

[jira] (MRELEASE-294) Generated release-pom.xml does not contain plugins configured in a super pom.

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

[jira] (MRELEASE-310) ForkedMavenExecutor assumes mvn is on command-line path

[ https://jira.codehaus.org/browse/MRELEASE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-310. --- Resolution: Duplicate Duplicate of MRELEASE-428, which was already fixed in version 2.0-beta-8

[jira] (MRELEASE-333) allowTimestampedSnapshots is not applied to report plugins

[ https://jira.codehaus.org/browse/MRELEASE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-333. --- Resolution: Incomplete No feedback from user, closing it as {{incomplete}}. > a

[jira] (MRELEASE-329) Parameter descriptions are incomplete

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

[jira] (MNG-4505) use slf4j to control various logging frameworks

[ https://jira.codehaus.org/browse/MNG-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292928#comment-292928 ] Baron Roberts commented on MNG-4505: >From my mailing list post: {quote} I'd like to replace the

[jira] (MEAR-148) In an ear which has skinny wars, want to include the same jar in shared lib of ear as well as in the war

[ https://jira.codehaus.org/browse/MEAR-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MNG-5254 to MEAR-148: -- Complexity: (was: Intermediate) Component/s: (was: Plugins and L

[jira] (SUREFIRE-844) "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)

[ https://jira.codehaus.org/browse/SUREFIRE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292922#comment-292922 ] Mark Ziesemer edited comment on SUREFIRE-844 at 2/28/12 10:33 AM: -

[jira] (SUREFIRE-844) "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)

[ https://jira.codehaus.org/browse/SUREFIRE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292923#comment-292923 ] Mark Ziesemer edited comment on SUREFIRE-844 at 2/28/12 10:34 AM: -

[jira] (SUREFIRE-844) "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)

[ https://jira.codehaus.org/browse/SUREFIRE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292924#comment-292924 ] Mark Ziesemer edited comment on SUREFIRE-844 at 2/28/12 10:34 AM: -

[jira] (SUREFIRE-844) "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)

[ https://jira.codehaus.org/browse/SUREFIRE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ziesemer updated SUREFIRE-844: --- Attachment: SUREFIRE-844-2.12.txt Debug output from "mvn clean test" on the attached test projec

[jira] (SUREFIRE-844) "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)

[ https://jira.codehaus.org/browse/SUREFIRE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ziesemer updated SUREFIRE-844: --- Attachment: SUREFIRE-844-2.11.txt Debug output from "mvn clean test" on the attached test projec

[jira] (SUREFIRE-844) "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)

[ https://jira.codehaus.org/browse/SUREFIRE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292923#comment-292923 ] Mark Ziesemer edited comment on SUREFIRE-844 at 2/28/12 10:33 AM: -

[jira] (SUREFIRE-844) "test" parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)

[ https://jira.codehaus.org/browse/SUREFIRE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ziesemer updated SUREFIRE-844: --- Attachment: SUREFIRE-844.zip Minimal test project demonstrating issue. > "test"

[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}

Martin Todorov created SUREFIRE-846: --- Summary: Maven surefire plugin creates two surefire* directories in the ${project.build.directory} Key: SUREFIRE-846 URL: https://jira.codehaus.org/browse/SUREFIRE-846

[jira] (MDEPLOY-147) deploy snapshot without timestamp

Lukasz Strzelecki created MDEPLOY-147: - Summary: deploy snapshot without timestamp Key: MDEPLOY-147 URL: https://jira.codehaus.org/browse/MDEPLOY-147 Project: Maven 2.x and 3.x Deploy Plugin

[jira] (SUREFIRE-745) -Dtest supports multiple test classes but not multiple test methods

[ https://jira.codehaus.org/browse/SUREFIRE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292906#comment-292906 ] Olivier Lamy edited comment on SUREFIRE-745 at 2/28/12 4:50 AM: f

[jira] (SUREFIRE-745) -Dtest supports multiple test classes but not multiple test methods

[ https://jira.codehaus.org/browse/SUREFIRE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SUREFIRE-745. - Resolution: Fixed Fix Version/s: 2.13 fixed r1294568. > -Dtest supports mult

[jira] (MEAR-147) wrong DOCTPYE in jboss-app.xml for 4.2

[ https://jira.codehaus.org/browse/MEAR-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-147. Resolution: Fixed Fixed. Thanks for the patch! > wrong DOCTPYE in jboss-app.xml for 4.2 >

[jira] (MEAR-147) wrong DOCTPYE in jboss-app.xml for 4.2

[ https://jira.codehaus.org/browse/MEAR-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MEAR-147 started by Stephane Nicoll. > wrong DOCTPYE in jboss-app.xml for 4.2 > -- > > Key: MEAR-147 >

[jira] (MEAR-147) wrong DOCTPYE in jboss-app.xml for 4.2

[ https://jira.codehaus.org/browse/MEAR-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-147: - Fix Version/s: 2.8 > wrong DOCTPYE in jboss-app.xml for 4.2 > --

[jira] (MCOMPILER-157) Maven Compiler Plugin should add to compileSourceRoots for next plugins to consider as source directory for generated files

[ https://jira.codehaus.org/browse/MCOMPILER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gleb Frank updated MCOMPILER-157: - Attachment: maven-compiler-plugin-addToSourcePathAsWell.patch For that matter, why not also add the