But normally the trunk should always contain a SNAPSHOT version, but only the submodules don't have it as parent as long as they don't need to rely on the changes in the parent. But if you use the release plugin to release the parent, will the tag contain only the parent or all the submodules as well? If I look at the maven plugins [1] tags the release contains all the modules (with SNAPSHOT-versions), but the tags directory also contains a tag for each release of the modules (without SNAPSHOT-versions).
So it seems they run mvn non recursively, but it is still tagging the whole tree. Seems a little strange to me. With regards, Nick Stolwijk -----Original Message----- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Mon 1/21/2008 11:39 AM To: Maven Users List Subject: Re: Best practices for seperate releases of parent and modules On Jan 21, 2008 11:00 AM, <[EMAIL PROTECTED]> wrote: > But when you release the parent, do you also release all the submodules or do > you run mvn with non-recursive? If the parent hasn't changed (in other words, if it hasn't a SNAPSHOT version), then I am happy to release the submodules only. To be honest, that "if" requires a certain degree of cautiousness. My recommended approach to resolve that is to provide read-only access to the parent for most developers except a few selected. Jochen -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett, Thief of Time) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
