[
https://issues.apache.org/jira/browse/MRAR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MRAR-33.
---------------------------------------
Resolution: Won't Do
> fileNameMapping for dependencies included in a RAR
> --------------------------------------------------
>
> Key: MRAR-33
> URL: https://issues.apache.org/jira/browse/MRAR-33
> Project: Maven Rar Plugin
> Issue Type: New Feature
> Affects Versions: 2.3, 2.4
> Reporter: Frank Lynch
> Priority: Major
> Attachments: patch.txt
>
>
> The attached patch adds a feature to support fileNameMappings for
> dependencies included in a rar.
> This is similar to the fileNameMapping feature in the maven-ear-plugin. In
> fact, much of the implementation was borrowed from there.
> There are three supported values for fileNameMapping: standard, no-version
> and full.
> standard - dependencies will be named as they usually are.
> eg: maven-artifact01-1.0-SNAPSHOT.jar
> no-version - dependencies will have their version information removed.
> eg: maven-artifact01.jar
> full - dependencies will be prefixed with their groupId.
> eg: org-apache-maven-test-maven-artifact01-1.0-SNAPSHOT.jar
>
> You can leverage this new capability using the fileNameMapping tag in the
> plugin configuration within your pom.xml
> eg:
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-rar-plugin</artifactId>
> <version>2.3</version>
> <configuration>
> <fileNameMapping>no-version</fileNameMapping>
> <includeJar>false</includeJar>
> </configuration>
> </plugin>
> </plugins>
> </build>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
