taojintianxia opened a new issue, #34094:
URL: https://github.com/apache/shardingsphere/issues/34094
### Preface
`maven remote resources plugin` is Inherited from apache parent pom
```xml
<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>
```
### Usage
```
Pull down resourceBundles containing remote resources and process the
resources contained inside. When that is done, the resources are injected into
the current (in-memory) Maven project, making them available to the
process-resources phase.
Resources that end in ".vm" are treated as Velocity templates. For those,
the ".vm" is stripped off for the final artifact name and it's fed through
Velocity to have properties expanded, conditions processed, etc...
```
### Why Disable
Apache JAR Resource Bundle are used for generating META-INF/DEPENDENCIES,
META-INF/LICENSE and META-INF/NOTICE , it contains templates for generating the
necessary license files and notices for all Apache releases.
remote resource plugin will invoke the Apache JAR Resource Bundle in release
process. so it should only be enabled in `release` profile
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
notifications-unsubscr...@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
