Can someone explain how releasing works with complex modules?
We have a top-level module which contains a tree of 20+ modules:
top/
one/
foo/
bar/
two/
something/
else/
How do version numbers work here - do all modules need to have the same
version as the 'top' parent pom? Will the release plugin ask me for the
version/tag/etc for each module when preparing? When I do a
release:perform, what is sync'd to the remote repository?
mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
