You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Wippermann (JIRA)" <ji...@apache.org> on 2018/01/24 15:51:00 UTC
[jira] [Updated] (MDEP-597) Copy goal resolves Parent POM
unnecessarily
[ https://issues.apache.org/jira/browse/MDEP-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Wippermann updated MDEP-597:
----------------------------------
Description:
I'm running {{dependency:copy }}via the CLI to download a .jar artifact. This leads to a long list of downloads during the plugin's execution since the artifact's POM, its Parent POM and all imported BOMs are resolved.
Is this really necessary? You might argue that downloading the artifact's POM is absolutely needed, but I don't see the point of resolving the parent (and the rest) as well.
was:
I'm running {dependency:copy} via the CLI to download a .jar artifact. This leads to a long list of downloads during the plugin's execution since the artifact's POM, its Parent POM and all imported BOMs are resolved.
Is this really necessary? You might argue that downloading the artifact's POM is absolutely needed, but I don't see the point of resolving the parent (and the rest) as well.
> Copy goal resolves Parent POM unnecessarily
> -------------------------------------------
>
> Key: MDEP-597
> URL: https://issues.apache.org/jira/browse/MDEP-597
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: copy
> Affects Versions: 3.0.2
> Reporter: Peter Wippermann
> Priority: Major
>
> I'm running {{dependency:copy }}via the CLI to download a .jar artifact. This leads to a long list of downloads during the plugin's execution since the artifact's POM, its Parent POM and all imported BOMs are resolved.
> Is this really necessary? You might argue that downloading the artifact's POM is absolutely needed, but I don't see the point of resolving the parent (and the rest) as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)