Can't you just define the version as variable and use it in your
webresource target path definition?
like in:
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.1</version>
<configuration>
....
<webResources>
<resource>
<!-- this is relative to the pom.xml directory -->
<directory>mycsssource/</directory>
<includes><include>**/*.css</include></includes>
<targetPath>${xyz.version}/</targetPath>
</resource>
</webResources>
</configuration>
</plugin>
On Tue, Jan 4, 2011 at 8:30 PM, juranta <juha.ra...@iki.fi> wrote:
>
> Yes, but my problem is that I need to use the version of one particular
> dependency while doing the filtering.
>
> Thanks,
>
> Juha
>
>> Assembly plugin can do resource filtering, see
>> http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/filtering-some-distribution-
>> files.html.
>
>>Kalle
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Accessing-the-version-of-a-dependency-tp3327490p3327642.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
