[
https://jira.codehaus.org/browse/MRESOURCES-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330625#comment-330625
]
Geoffrey De Smet commented on MRESOURCES-31:
--------------------------------------------
We have a use case related to osgi/karaf.
We have a filtered features.xml file which needs to be able to use
{code}
${project.dependencies["org.mvel:mvel"].version}
{code}
Note: we can't declare a property ${verson.mvel}, because we're getting most of
our dependency versions (including this one) by importing a single target
platform bom.
> Dependency resolution for resource filtering
> --------------------------------------------
>
> Key: MRESOURCES-31
> URL: https://jira.codehaus.org/browse/MRESOURCES-31
> Project: Maven Resources Plugin
> Issue Type: Wish
> Affects Versions: 2.2
> Reporter: Daniel Holmen
> Priority: Minor
>
> I've been trying to use the project.compileClasspathElements property in a
> filtered resource, but discovered that Resources plugin isn't set up to
> require dependency resolution. The result of this is that i cannot use any of
> the classpath properties in my filtered resources.
> The solution is quite simple, just add a @requiresDependencyResolution
> annotation to ResourcesMojo. I have no idea if this causes any bad
> side-effects - but it seemed to work properly when I tested it locally.
--
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
