Craig is spot on here - you use nextVersion-SNAPSHOT in both currentVersion ad dependency versions until it is released.
Some extra things to note: - jar:deploy-snapshot is deprecated. In the latest artifact plugin, jar:deploy will behave that way if the version contains SNAPSHOT, or behave like a release otherwise - you can avoid multiple updates to dependencies by using inheritence. For dependencies used everywhere, you can inherit the actual dependency. For deps that just want the same version wherever used, use a jar override with a version. If you use this feature, be sure to use the latest Artifact plugin available for your version of Maven - it will make better POMs in the repo that will help if converting to m2 later. - you also don't need to synchronize versions - there is no harm in keeping to the minimum version required, and just updating to the SNAPSHOT where used, or in assemblies such as WAR or executable distributions (as they must meet the requirements of all dependencies) - if you use the latter approach, the multiproject report will show you what versions are out of sync. - finally, scm:prepare-release eases the process of releasing a component - however it doesn't look after SNAPSHOTs (something that is improved in m2, just like all of the above :) Hope this helps! - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
