Thanks, that's a simple solution that might even work in most of the situations (perhaps excepting the release plugin, etc).
I also found a more complex way to access the versions of a dependency using Groovy plugin. For those who are interested: <plugins> <plugin> <groupId>org.codehaus.groovy.maven</groupId> <artifactId>gmaven-plugin</artifactId> <version>1.0-rc-5</version> <executions> <execution> <phase>validate</phase> <goals> <goal>execute</goal> </goals> <configuration> <source> print project.dependencies; for ( i in project.dependencies ) { project.properties[ 'depinfo.' + i['groupId'] + '.' + i['artifactId'] + '.version' ] = i['version']; } </source> </configuration> </execution> </executions> </plugin> Then you can access ${depinfo.mygroup.myartifact.version}... But I'll try to go with your suggestion. Juha > Right, and the rest of your build needs to know that version as well, > right? Put that version in a property and use it in the dependency as > well as resource filtering, i.e. > <properties> > <cssversion>2</cssversion> > </properties> > > Kalle -- View this message in context: http://maven.40175.n5.nabble.com/Accessing-the-version-of-a-dependency-tp3327490p3329171.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