You can still define properties in parent POMs of course: <properties> <my.lib.version>3.2</my.lib.version> </properties>, then use <version>$

</version>.

I believe Guillaume is referring to the exec-war and exec-war-only goals, as those seem to be the only two with those options. I don't know what the difference is between warRunDependency and extraDependency (the docs don't define the former: http://tomcat.apache.org/maven-plugin-2.1-SNAPSHOT/tomcat7-maven-plugin/exec-war-mojo.html.) Also, I'm not sure what types of dependencies would need to be placed in the Tomcat root classloader and not just with the web application itself (i.e., can't Guillaume just declare these as normal <dependencies/> within the WAR so the version numbers can be taken care of that way?) Although this suggestion does have merit, arguably it may not be worth the effort if it is so rarely used and <properties/> can be used instead, further, as a drawback it might cause more people to incorrectly over-use this functionality instead of properly defining the <dependencies/> with the WAR itself.

Hi,

you are right this case is only for the the exec-war and exec-war-only goals.

Here my situation, I want to package several wars in one exec-war, so I have created a pom project which depends on these 2 wars and use the tomcat7-maven-plugin. The version of my war are declared in the dependencyManagement of my parent pom. That give me the following structure :
parent project
-> project war 1
-> project war 2
-> packaging project and tomcat plugin

This way when I release the parent all the versions are correctly set (which is not the case if I use a property). The warRunDependcy needs a version number, so when i release my project the versiond of my wars are not change in the plugin configuration.

And it's the same when i use the extraDependency (which include some library to the tomcat like the database driver or some specific stuffs).

any sample project?

FAILURE: Integrated in TomcatMavenPlugin-mvn3.x #268 (See https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/268/)
MTOMCAT-196 for warRunDependencies too (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1539227)

• /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java
• /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractStandaloneWarMojo.java
  MTOMCAT-196 Add the possiblilty to search warRunDepencies and extraDependcies throug the dependencyManagement (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1539226)
• /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java