[jira] [Commented] (MNG-6101) Dependency plugin bypasses reactor when resolving dependencies
[
https://issues.apache.org/jira/browse/MNG-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187956#comment-17187956
]
Martin Kanters commented on MNG-6101:
-
I'm not sure if it was common knowledge already, but I've verified that phases
earlier in the lifecycle than compile (such as validate) do not build the
reactor.
It's not a proper solution, but you could check if skipping compilation is good
enough:
{{mvn compile dependency:tree -Dmaven.main.skip}}
> Dependency plugin bypasses reactor when resolving dependencies
> --
>
> Key: MNG-6101
> URL: https://issues.apache.org/jira/browse/MNG-6101
> Project: Maven
> Issue Type: Bug
> Components: Dependencies, Reactor and workspace
>Affects Versions: 3.3.9
>Reporter: Tuure Laurinolli
>Priority: Major
> Fix For: 3.x / Backlog
>
> Attachments: resolution.zip
>
>
> When running {{mvn dependency:tree}} on a multi-module project, inter-module
> dependencies are not resolved through reactor. Using another goal in the same
> build (e.g. {{mvn compile dependency:tree}}) as suggested in
> http://www.mail-archive.com/users@maven.apache.org/msg104341.html resolves
> the immediate issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6101) Dependency plugin bypasses reactor when resolving dependencies
[
https://issues.apache.org/jira/browse/MNG-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187732#comment-17187732
]
Michael Osipov commented on MNG-6101:
-
[~rfscholte] to the rescue
> Dependency plugin bypasses reactor when resolving dependencies
> --
>
> Key: MNG-6101
> URL: https://issues.apache.org/jira/browse/MNG-6101
> Project: Maven
> Issue Type: Bug
> Components: Dependencies, Reactor and workspace
>Affects Versions: 3.3.9
>Reporter: Tuure Laurinolli
>Priority: Major
> Fix For: 3.x / Backlog
>
> Attachments: resolution.zip
>
>
> When running {{mvn dependency:tree}} on a multi-module project, inter-module
> dependencies are not resolved through reactor. Using another goal in the same
> build (e.g. {{mvn compile dependency:tree}}) as suggested in
> http://www.mail-archive.com/users@maven.apache.org/msg104341.html resolves
> the immediate issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6101) Dependency plugin bypasses reactor when resolving dependencies
[
https://issues.apache.org/jira/browse/MNG-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187580#comment-17187580
]
Tuure Laurinolli commented on MNG-6101:
---
What would be the cheapest way to make sure reactor gets built? Compile is
fairly expensive.
> Dependency plugin bypasses reactor when resolving dependencies
> --
>
> Key: MNG-6101
> URL: https://issues.apache.org/jira/browse/MNG-6101
> Project: Maven
> Issue Type: Bug
> Components: Dependencies, Reactor and workspace
>Affects Versions: 3.3.9
>Reporter: Tuure Laurinolli
>Priority: Major
> Fix For: 3.x / Backlog
>
> Attachments: resolution.zip
>
>
> When running {{mvn dependency:tree}} on a multi-module project, inter-module
> dependencies are not resolved through reactor. Using another goal in the same
> build (e.g. {{mvn compile dependency:tree}}) as suggested in
> http://www.mail-archive.com/users@maven.apache.org/msg104341.html resolves
> the immediate issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6101) Dependency plugin bypasses reactor when resolving dependencies
[
https://issues.apache.org/jira/browse/MNG-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17186817#comment-17186817
]
Michael Osipov commented on MNG-6101:
-
This is not a problem with the Dependency Plugin, this case applies to all
plugins which are not run together with a phase which builds the reactor.
> Dependency plugin bypasses reactor when resolving dependencies
> --
>
> Key: MNG-6101
> URL: https://issues.apache.org/jira/browse/MNG-6101
> Project: Maven
> Issue Type: Bug
> Components: Dependencies, Reactor and workspace
>Affects Versions: 3.3.9
>Reporter: Tuure Laurinolli
>Priority: Major
> Fix For: 3.x / Backlog
>
> Attachments: resolution.zip
>
>
> When running {{mvn dependency:tree}} on a multi-module project, inter-module
> dependencies are not resolved through reactor. Using another goal in the same
> build (e.g. {{mvn compile dependency:tree}}) as suggested in
> http://www.mail-archive.com/users@maven.apache.org/msg104341.html resolves
> the immediate issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6101) Dependency plugin bypasses reactor when resolving dependencies
[
https://issues.apache.org/jira/browse/MNG-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741696#comment-16741696
]
Sylwester Lachiewicz commented on MNG-6101:
---
Still valid with Maven 3.6.1-SNAPSHOT and maven-dependency-plugin:2.8
> Dependency plugin bypasses reactor when resolving dependencies
> --
>
> Key: MNG-6101
> URL: https://issues.apache.org/jira/browse/MNG-6101
> Project: Maven
> Issue Type: Bug
> Components: Dependencies, Reactor and workspace
>Affects Versions: 3.3.9
>Reporter: Tuure Laurinolli
>Priority: Major
> Fix For: 3.x / Backlog
>
> Attachments: resolution.zip
>
>
> When running {{mvn dependency:tree}} on a multi-module project, inter-module
> dependencies are not resolved through reactor. Using another goal in the same
> build (e.g. {{mvn compile dependency:tree}}) as suggested in
> http://www.mail-archive.com/users@maven.apache.org/msg104341.html resolves
> the immediate issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
