Ticket #218 (new defect)
maven-release-plugin fails on unmatched depending module version numbers
|Reported by:||mpo||Owned by:||bruno|
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.
TODO: describe more clearly the experienced build-behaviour (failure) and known workaround. (Bert?)