maven-release-plugin fails on unmatched depending module version numbers

[mpo]

When building a new release of some kauri-based application using the maven-release plugin the pom.xml files are all automatically updated for the new 'upcoming' version numbers. In this process however the conf/wiring.xml and classloader.xml are not updated yielding to a failed/bad build.

One way of tackling might come from making the @version indications optional as done for the kauri-dependencies (mentioned in #34 and #45)

TODO: describe more clearly the experienced build-behaviour (failure) and known workaround. (Bert?)

[bc]

In order to get the correct version in the wiring.xml you can change it to the release version before releasing. (not the best solution)
The problem is that, when doing this, you get an error "Error resolving artifact listed in wiring.xml" (because the version you specified in the wiring.xml is never build).

You can work around this by

• changing the version in the pom to the release version
  
• build the project
  
• change the version in the pom back to the original version
  
• release using the release plugin
  

(but this definitely doesn't seem like a good solution)