[jira] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324916#comment-324916 ] Eric Pabst commented on MDEP-410: - In this case, since it's a new goal, couldn't it be marked as "onl

[jira] (MDEP-156) dependency:analyze mistakenly reports an implemented interface as an unused, declared dependency

[ https://jira.codehaus.org/browse/MDEP-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MDEP-156: --- Description: When executing dependency:analyze on my project, analyze mistakenly identifies a compile time

[jira] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324915#comment-324915 ] Herve Boutemy commented on MDEP-410: like MDEP-409, the problem is that it will require Maven 3

[jira] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MDEP-410: --- Comment: was deleted (was: These are the same diff again, but renamed for convenience. Someone can delete

[jira] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MDEP-410: --- Attachment: (was: collect-mojo.patch) > dependency:resolve fails for a multi-module project where on

[jira] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MDEP-410: --- Attachment: (was: collect-mojo.diff) > dependency:resolve fails for a multi-module project where one

[jira] (MDEP-409) dependency:tree fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324914#comment-324914 ] Herve Boutemy commented on MDEP-409: yes, this is the solution the only drawback is to require Ma

[jira] (MPIR-229) The 'modules' report does not support 'url' elements using properties.

[ https://jira.codehaus.org/browse/MPIR-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MPIR-229: --- Attachment: MPIR-229.patch Patch updating the IT to demonstrate the issue. Applying this patch and

[jira] (MPIR-229) The 'modules' report does not support 'url' elements using properties.

[ https://jira.codehaus.org/browse/MPIR-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324907#comment-324907 ] Robert Scholte commented on MPIR-229: - I've created an IT at [r1481042|http://svn.apache.org/r148

[jira] (MDEP-409) dependency:tree fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pabst updated MDEP-409: Attachment: MDEP-409.patch Also available as a github pull request: [https://github.com/epabst/maven-plugins/pull

[jira] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pabst updated MDEP-410: Attachment: MDEP-410-maven-plugins-aggregator.patch MDEP-410-maven-plugins-aggregator.diff These a

[jira] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324903#comment-324903 ] Eric Pabst edited comment on MDEP-410 at 5/10/13 7:44 AM: -- Here is a patch o

[jira] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://jira.codehaus.org/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pabst updated MDEP-410: Attachment: collect-mojo.diff collect-mojo.patch Here is a patch or diff that includes adding a de