[jira] [Commented] (MNG-5849) maven can not be found when current directory is drive/root at least on windows 7 64bit

[ https://issues.apache.org/jira/browse/MNG-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098725#comment-15098725 ] Miriam Lee commented on MNG-5849: - Possible duplicate of MNG-5796 > maven can not be found

[jira] [Created] (MNGSITE-273) Typo on the History of Maven webpage

Richard Lynn Paul created MNGSITE-273: - Summary: Typo on the History of Maven webpage Key: MNGSITE-273 URL: https://issues.apache.org/jira/browse/MNGSITE-273 Project: Maven Project Web Site

[jira] [Commented] (MNG-5961) Maven possibly not aware of log4j2

[ https://issues.apache.org/jira/browse/MNG-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098236#comment-15098236 ] Arnaud HERITIER commented on MNG-5961: -- ok thanks [~michael-o] I didn't notice it > Ma

[jira] [Commented] (MSHADE-218) MANIFEST entries copied from a custom execution-ed jar

[ https://issues.apache.org/jira/browse/MSHADE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098229#comment-15098229 ] Jin Kwon commented on MSHADE-218: - When I change the custom {{jar}}'s phase to {{prepare-p

[jira] [Created] (MSHADE-218) MANIFEST entries copied from a custom execution-ed jar

Jin Kwon created MSHADE-218: --- Summary: MANIFEST entries copied from a custom execution-ed jar Key: MSHADE-218 URL: https://issues.apache.org/jira/browse/MSHADE-218 Project: Maven Shade Plugin Issue

[jira] [Reopened] (MNG-5359) Declared execution in PluginMgmt gets bound to lifecycle (regression)

[ https://issues.apache.org/jira/browse/MNG-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte reopened MNG-5359: Re-opening for further discussion. This probably cannot be fixed without breaking Maven 3 backwar

[jira] [Commented] (MNG-5359) Declared execution in PluginMgmt gets bound to lifecycle (regression)

[ https://issues.apache.org/jira/browse/MNG-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098170#comment-15098170 ] Hudson commented on MNG-5359: - SUCCESS: Integrated in maven-3.x #1191 (See [https://builds.apac

[jira] [Commented] (MNG-5962) mvn fails when the current directory has spaces in between

[ https://issues.apache.org/jira/browse/MNG-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098078#comment-15098078 ] Hudson commented on MNG-5962: - SUCCESS: Integrated in maven-3.x #1190 (See [https://builds.apac

[jira] [Closed] (MNG-5962) mvn fails when the current directory has spaces in between

[ https://issues.apache.org/jira/browse/MNG-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-5962. -- Resolution: Fixed Fix Version/s: 3.4.0 Patch [a035d9026f45518f430dace7ba930835d0d3e85a|htt

[jira] [Assigned] (MNG-5962) mvn fails when the current directory has spaces in between

[ https://issues.apache.org/jira/browse/MNG-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte reassigned MNG-5962: -- Assignee: Christian Schulte > mvn fails when the current directory has spaces in between

[jira] [Updated] (MDEP-515) Unpack does not work on Linux

[ https://issues.apache.org/jira/browse/MDEP-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-515: - Description: I had the following plugin configuration for maven-dependency-plugin: {code:xml

[jira] [Commented] (MJAR-62) Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar

[ https://issues.apache.org/jira/browse/MJAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098038#comment-15098038 ] Michael Osipov commented on MJAR-62: Maven version [3.3.1|https://issues.apache.org/jira

[jira] [Updated] (MDEP-515) Unpack does not work on Linux

[ https://issues.apache.org/jira/browse/MDEP-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-515: - Description: I had the following plugin configuration for maven-dependency-plugin: {code:xml

[jira] [Commented] (MJAR-62) Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar

[ https://issues.apache.org/jira/browse/MJAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098039#comment-15098039 ] Michael Osipov commented on MJAR-62: Maven version [3.3.1|https://issues.apache.org/jira

[jira] [Issue Comment Deleted] (MJAR-62) Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar

[ https://issues.apache.org/jira/browse/MJAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MJAR-62: --- Comment: was deleted (was: Maven version [3.3.1|https://issues.apache.org/jira/secure/ReleaseNote.jspa?p

[jira] [Commented] (MNG-5961) Maven possibly not aware of log4j2

[ https://issues.apache.org/jira/browse/MNG-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098035#comment-15098035 ] Michael Osipov commented on MNG-5961: - I have changed the fix version to 3.4.0 because {

[jira] [Updated] (MNG-5961) Maven possibly not aware of log4j2

[ https://issues.apache.org/jira/browse/MNG-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-5961: Fix Version/s: (was: 3.3.10) 3.4.0 > Maven possibly not aware of log4j2 > -

[jira] [Created] (MDEP-515) Unpack does not work on Linux

Karl Heinz Marbaise created MDEP-515: Summary: Unpack does not work on Linux Key: MDEP-515 URL: https://issues.apache.org/jira/browse/MDEP-515 Project: Maven Dependency Plugin Issue Type:

[jira] [Resolved] (MNG-5961) Maven possibly not aware of log4j2

[ https://issues.apache.org/jira/browse/MNG-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud HERITIER resolved MNG-5961. -- Resolution: Fixed Yes it is exactly what I just fixed in master (thus for 3.3.10) with the commit

[jira] [Updated] (MNG-5961) Maven possibly not aware of log4j2

[ https://issues.apache.org/jira/browse/MNG-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud HERITIER updated MNG-5961: - Fix Version/s: 3.3.10 > Maven possibly not aware of log4j2 > -- > >

[jira] [Assigned] (MNG-5961) Maven possibly not aware of log4j2

[ https://issues.apache.org/jira/browse/MNG-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud HERITIER reassigned MNG-5961: Assignee: Arnaud HERITIER > Maven possibly not aware of log4j2 >

[jira] [Comment Edited] (MNG-5961) Maven possibly not aware of log4j2

[ https://issues.apache.org/jira/browse/MNG-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097881#comment-15097881 ] Michael Osipov edited comment on MNG-5961 at 1/14/16 9:31 AM: --

[jira] [Commented] (MNG-5961) Maven possibly not aware of log4j2

[ https://issues.apache.org/jira/browse/MNG-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097881#comment-15097881 ] Michael Osipov commented on MNG-5961: - I think this is a duplicate of MNG-3507. > Maven

[jira] [Resolved] (MPLUGINTESTING-47) Incorrect Mojo Java5 annotations in example

[ https://issues.apache.org/jira/browse/MPLUGINTESTING-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar resolved MPLUGINTESTING-47. - Resolution: Fixed Fix Version/s: next-release Fixed in 4a374fc5a308a

[jira] [Assigned] (MPLUGINTESTING-47) Incorrect Mojo Java5 annotations in example

[ https://issues.apache.org/jira/browse/MPLUGINTESTING-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar reassigned MPLUGINTESTING-47: --- Assignee: Anders Hammar > Incorrect Mojo Java5 annotations in example