maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MPOM-218) consider impact of maven-remote-resources-plugin in plugins not pluginManagement
Date Tue, 06 Aug 2019 00:00:00 GMT

    [ https://issues.apache.org/jira/browse/MPOM-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900492#comment-16900492
] 

Christopher Tubbs commented on MPOM-218:
----------------------------------------

In Accumulo, we just just provide a basic "DEPENDENCIES" file. The plugin doesn't clobber
the one that already exists: https://github.com/apache/accumulo/blob/rel/2.0.0/DEPENDENCIES

> 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
>            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
(v7.6.14#76016)

Mime
View raw message