[
https://jira.codehaus.org/browse/MRAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325182#comment-325182
]
Florian Fray commented on MRAR-30:
----------------------------------
Just faced the same problem, so I'm using this configuration as workaround:
{noformat}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-rar-plugin</artifactId>
<configuration>
<filterRarSourceDirectory>true</filterRarSourceDirectory>
<raXmlFile>${rarSourceDirectory}/META-INF/nonexistent-ra.xml</raXmlFile>
<warnOnMissingRaXml>false</warnOnMissingRaXml>
</configuration>
<executions>
<execution>
<id>rar</id>
<goals>
<goal>rar</goal>
</goals>
</execution>
</executions>
</plugin>
{noformat}
> Filtering of RA.xml
> -------------------
>
> Key: MRAR-30
> URL: https://jira.codehaus.org/browse/MRAR-30
> Project: Maven 2.x Rar Plugin
> Issue Type: New Feature
> Affects Versions: 2.2
> Environment: Win7 64Bit JDK1.6.0_26
> Reporter: Markus KARG
> Priority: Minor
>
> It would be great if one could specify <filtering>true</filtering> in the
> pom.xml to make the RAR plugin filter the custom RA.xml file provided in src.
> Using this feature, one could put ${project.version} into the custom RA.xml's
> <resourceadapter-version/> section.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
