Either you release the whole module hierarchy starting from the parent release, or you use a non-snapshot dependency for the parent. As a rule of thumb, you use a separate version for a master pom without modules (such as a company-wide pom) and the same version for a multi-module project, releasing everything at the same time.
Kalle On Sun, Aug 3, 2008 at 3:32 PM, sverhagen <[EMAIL PROTECTED]> wrote: > > We like Continuous Integration, so we set the parent.version of our > sub-modules to the latest snapshot of their parent. > When we go and release:prepare some sub-module, it'll complain about this > snapshot, attempt to bump the parent to the first next release, and fail > during release:perform, because the parent has not really been released at > that next release version. > > How are people dealing with this? > -- > View this message in context: > http://www.nabble.com/Parent-version%3A-release-vs.-Continuous-Integration-tp18803181p18803181.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
