mvn release doesn't play well with mvn kauripackage:package

[mpo]

When one uses the mvn release plugin the versions in the pom.xml's get automatically updated and committed to your project's scm system (with a specific created tag as well)

From there the updated version tags will end up in the generated classloader.xml files of your kauri modules, so that is covered.

However typically there will still be a number of version references to your own jars in the conf/kauri/wiring.xml. The packaging plugin will assemble those into your kauri-package so there is an issue there.

Today the (manual) workaround is in a good description of the release-process for your project and making sure the references to the wiring.xml are updated to your 'intended' release-name prior to running the mvn-release cycle (indeed: else the tagged version will not be holding the correct wiring.xml and will thus not be a good source for rebuilding your package)

Unsure ATM what we can do about it that automates this better, some suggestions:

• [build-time] add some plugin that updates the wiring.xml based on the version in the pom. This approach will require a subtle selection of the goal during release to let it work upon. Try outs /suggestions based on ant plugin or mvn filtering are welcome.
• [run-time] add some way for the run-time to retrieve the needed version numbers from somewhere else then the wiring.xml (system property injected from the service wrapper? Still formally declared in the wiring.xml?). This approach still will need some build-time thinkering to inject that version number in the wrapper though.

[mpo]

See ​http://docs.outerthought.org/kauri-docs-0_4/282-kauri/285-kauri.html for more on the packaging plugin.

Probably a good place for some doc updates if/when this is fixed.