[jira] (MNG-5293) Maven 3.0.4 crashes when -Djava.net.useSystemProxies=true added.

[ https://jira.codehaus.org/browse/MNG-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300595#comment-300595 ] denixx baykin commented on MNG-5293: I tried 3.0.3. All the same. Maybe it's a JRE issue, not

[jira] (MNG-5293) Maven 3.0.4 crashes when -Djava.net.useSystemProxies=true added.

[ https://jira.codehaus.org/browse/MNG-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] denixx baykin updated MNG-5293: --- Attachment: maven java netbeans libdbus crash2.txt backtrace with 3.0.3 Maven 3.0.4

[jira] (MNG-5293) Maven 3.0.4 crashes when -Djava.net.useSystemProxies=true added.

[ https://jira.codehaus.org/browse/MNG-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300596#comment-300596 ] denixx baykin edited comment on MNG-5293 at 6/8/12 1:12 AM: See maven

[jira] (MNG-5293) Maven 3.0.4 crashes when -Djava.net.useSystemProxies=true added.

[ https://jira.codehaus.org/browse/MNG-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300596#comment-300596 ] denixx baykin edited comment on MNG-5293 at 6/8/12 1:12 AM: See maven

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Petrelli updated MRELEASE-760: -- Attachment: mrelease760-patch.diff The bug is still there even with the current fix, that

[jira] (MNG-2315) Add option to exclude all transitive dependencies for a particular one

[ https://jira.codehaus.org/browse/MNG-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300608#comment-300608 ] Samuel Langlois commented on MNG-2315: -- Like the 134 other people who voted for it, I'd love to

[jira] (SCM-667) mvn release:prepare fails for hierarchical multi-module project on Windows 7 using msysgit with is outside repository

[ https://jira.codehaus.org/browse/SCM-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300611#comment-300611 ] Jiri Peinlich commented on SCM-667: --- Hi, in our project we still faced this (or very similar)

[jira] (SCM-667) mvn release:prepare fails for hierarchical multi-module project on Windows 7 using msysgit with is outside repository

[ https://jira.codehaus.org/browse/SCM-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300611#comment-300611 ] Jiri Peinlich edited comment on SCM-667 at 6/8/12 6:02 AM: --- Hi, in our

[jira] (MRELEASE-769) Release:prepare fails on Windows when commonBaseDir of all reactor projects is root drive (e.g. D:\)

Conan Cook created MRELEASE-769: --- Summary: Release:prepare fails on Windows when commonBaseDir of all reactor projects is root drive (e.g. D:\) Key: MRELEASE-769 URL: https://jira.codehaus.org/browse/MRELEASE-769

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reopened MRELEASE-760: - updateWorkingCopyVersions=false still bumps up pom versions to next development version

[jira] (MPMD-151) Use canonical paths for the file list / Unit test failures on builds.apache.org

[ https://jira.codehaus.org/browse/MPMD-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MPMD-151. - Resolution: Fixed Fix Version/s: 2.8 Assignee: Olivier Lamy Good catch. Some ASF Jenkins nodes

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-760. --- Resolution: Fixed Fixed in [r1348226|http://svn.apache.org/viewvc?rev=1348226view=rev]. Thanks

[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:all-tabpanel ] Robert Scholte updated MRELEASE-663: Description: Co-worker ran into issues where if he had checked out his project directly in

[jira] (MRELEASE-769) Release:prepare fails on Windows when commonBaseDir of all reactor projects is root drive (e.g. D:\)

[ https://jira.codehaus.org/browse/MRELEASE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-769. --- Resolution: Duplicate Assignee: Robert Scholte Release:prepare fails on Windows when

[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:all-tabpanel ] Robert Scholte closed MRELEASE-663. --- Resolution: Fixed Fix Version/s: 2.3.2 Assignee: Robert Scholte Fixed in

[jira] (MRELEASE-573) cannot release a multi-module project with maven3

[ https://jira.codehaus.org/browse/MRELEASE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-573: Description: {{release:prepare}} produces the following exception. I am releasing a multi

[jira] (MRELEASE-573) cannot release a multi-module project with maven3

[ https://jira.codehaus.org/browse/MRELEASE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-573. --- Resolution: Cannot Reproduce Assignee: Robert Scholte I've done several releases with