[jira] [Commented] (MPOM-218) consider impact of maven-remote-resources-plugin in plugins not pluginManagement

["Herve Boutemy (Jira)" <ji...@apache.org>]

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

Herve Boutemy commented on MPOM-218:
------------------------------------

yes, there is an execution that has been defined intentionally 12 years ago to run: here is the code
{code:xml}
      <!-- We want to package up license resources in the JARs produced -->
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-remote-resources-plugin</artifactId>
        <executions>
          <execution>
            <id>process-resource-bundles</id>
            <goals>
              <goal>process</goal>
            </goals>
            <configuration>
              <resourceBundles>
                <resourceBundle>org.apache:apache-jar-resource-bundle:1.4</resourceBundle>
              </resourceBundles>
            </configuration>
          </execution>
        </executions>
      </plugin>
{code}
using the Apache jar resource bundle https://maven.apache.org/apache-resource-bundles/index.html#jar-resource-bundle-and-incubator-disclaimer-resource-bundle

it was added in https://github.com/apache/maven-apache-parent/commit/b6d76ce21b88c46a95e4c851d9da47013972152b

I must admit I don't really know the content, what would be the consequence of simply removing that config, or if we can make it easily configurable

> 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
(v8.20.1#820001)