[
https://jira.codehaus.org/browse/MRRESOURCES-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356746#comment-356746
]
Karl-Heinz Marbaise commented on MRRESOURCES-83:
------------------------------------------------
If you change the name of the {{beans.xml}} file into {{beans.xml.vm}} and
change the includes in bundle pom accordingly your test will be succesfully.
The problem seemed to be located in the documentation (excerpt from docs of the
process goal:
{quote}
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...
Resources that don't end in ".vm" are copied "as is".
{quote}
> Cannot filter ${project.version}
> --------------------------------
>
> Key: MRRESOURCES-83
> URL: https://jira.codehaus.org/browse/MRRESOURCES-83
> Project: Maven Remote Resources Plugin
> Issue Type: Bug
> Affects Versions: 1.5
> Environment: Maven 3.0.5
> Windows 7 x64
> java version "1.7.0_51"
> Reporter: Falko Modler
> Attachments: MRRESOURCES-83.zip
>
>
> The plugin goal {{process}} fails to filter {{$\{project.version\}}} in a
> file named {{META-INF/beans.xml}} which comes from a bundle created in
> another module via maven-remote-resources-plugin.
> I tried setting {{includeProjectProperties}} to true but that did not help.
> Even trying a custom {{testproperty}} did not yield the desired effect.
> Please see the attached test case project which contains two modules:
> - {{bundle}} packages the file with the placeholder
> - {{process}} uses the bundle and tries to have the placeholder filtered (see
> {{MRRESOURCES83Test}})
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
