I commented it out in the script for now, as it is not really needed given that all of the EMA code used to build this project is in the same repository. If (when) we separate some of these components out into separate projects, we'll need to add back a similar usage of mvn:versions in the release script so that the any EMA snapshot versions referenced will be updated to latest non-snapshot before doing the release with the plugin. This avoids annoying multiple command line prompts to update to released versions when running a release.
Once we get to that stage, we can update the release script accordingly to handle this behavior. Closing this issue now, as I was just able to do a release of 0.9.0 using the script.
I figured out that this usage of mvn:versions in release.sh (https://github.com/esbtools/esb-message-admin/blob/master/release.sh#L36) was causing all dependencies to get updated to the latest version, which generally resulted in test failures and/or compilation errors.
I commented it out in the script for now, as it is not really needed given that all of the EMA code used to build this project is in the same repository. If (when) we separate some of these components out into separate projects, we'll need to add back a similar usage of mvn:versions in the release script so that the any EMA snapshot versions referenced will be updated to latest non-snapshot before doing the release with the plugin. This avoids annoying multiple command line prompts to update to released versions when running a release.
Once we get to that stage, we can update the release script accordingly to handle this behavior. Closing this issue now, as I was just able to do a release of 0.9.0 using the script.