maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Boué (JIRA) <j...@apache.org>
Subject [jira] [Closed] (MDEP-573) "purge-local-repository -Dinclude" does not work as described
Date Sat, 01 Jul 2017 13:58:00 GMT

     [ https://issues.apache.org/jira/browse/MDEP-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guillaume Boué closed MDEP-573.
-------------------------------
       Resolution: Fixed
         Assignee: Guillaume Boué
    Fix Version/s: next-release

> "purge-local-repository -Dinclude" does not work as described
> -------------------------------------------------------------
>
>                 Key: MDEP-573
>                 URL: https://issues.apache.org/jira/browse/MDEP-573
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: purge-local-repository
>    Affects Versions: 3.0.0, 3.0.1
>         Environment: Win 7, 64 Bit, JDK 8u92, MVN 3.5.0, MDEP 3.0.1
>            Reporter: Markus Karg
>            Assignee: Guillaume Boué
>             Fix For: next-release
>
>
> When I run _mvn generate-sources_ on a POM which binds the goal _purge-local-repository_
to that phase, then MDEP correctly purges and re-resolves the all dependencies of all submodules.
> When I instead run _mvn dependency:purge-local-repository_ then the reactor *skips* all
submodules.
> This in rather annoying and surprising, because nowhere in the public description of
MDEP is told that invoking _dependency:purge-local-repository_ at the command line as the
sole goal will effectively *skip submodules* of the POM.
> If this is not intended, this bug should get fixed.
> If this is intended, then the documentation of this goal should clearly tell that.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message