Page History

...

For more details on this example, see the Camel Example.

Version resolving

In the example above you can see we just list the maven groupId and artifactId strings for the various JBI deployment artifacts (shared libraries, components, service assemblies etc). You can if you prefer specify the full file, or specify the explicit version number.

However its common to want to just inherit the version number from the maven pom.xml. So if you omit the version property on the above deployment elements, it will search the classpath for the META-INF/maven/dependencies.properties files and look in those to try figure out the version number of the referenced groupId and artifactId.

So just add the necessary test dependencies to your maven pom.xml and you can then avoid specifying the version numbers in your spring.xml