[
https://issues.apache.org/jira/browse/MPOM-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPOM-218:
-------------------------------
Affects Version/s: ASF-24
ASF-16
> consider impact of maven-remote-resources-plugin in plugins not
> pluginManagement
> ---------------------------------------------------------------------------------
>
> Key: MPOM-218
> URL: https://issues.apache.org/jira/browse/MPOM-218
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
> Affects Versions: ASF-16, ASF-24
> Reporter: Adrian Cole
> Priority: Major
>
> While maven-remote-resources-plugin in plugins, it is difficult to work with
> vs if it were in pluginManagement. For example, the parent pom can spit out a
> distracting empty DEPENDENCIES file, which ends up by default in the source
> distribution.
> I've noticed multiple projects (ex dubbo, edgent) creating separate
> distribution modules which on one hand works around this issue, but on the
> other is a source of maintenance.
> I'd ask to consider using pluginManagement instead, or possibly having the
> ability to not create a DEPENDENCIES file when there are none, which would
> also solve the problem. Maybe there's also another way to strip this out with
> an assembly, but I've failed to figure this out.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
