On Sat, Feb 23, 2008 at 9:56 AM, deckrider <[EMAIL PROTECTED]> wrote: > We have a number of multi module projects with multiple branches. > Unfortunately, this means that every time we use release:prepare > release:perform, it updates all the poms, which then appear in another > branch (and must be ignored) when we run svnmerge. > > Is there some technique to easily ignore these changes, but pickup > other needed pom.xml changes?
What's happening exactly? I'm not familiar with the svnmerge tool. Is it *any* update to the poms that causes a problem, or is it the incremented version number after the release? (If it's the latter, you don't _have_ to increment/change the "next" version number.) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
