Hi,

I try to use mvn release in a multi-module build scenario but I'm not sure whether I go into the right direction.
Our standalone projects have the following structure:

projA
       \_trunk
       \_tags
       \_branches

We also have some multi module projects and I wonder what is the best way to structure these to be able to run a "mvn release:perform" on the module build pom?

My first thought was to have trunk/tags/branches on the module-parent as well:

moduleBuild
                   \_trunk
| \_pom.xml (which defines the modules via ../projA/trunk etc.)
                    \_tags
                    \_branches
                    \_projA
                               \_trunk
                               \_tags
                               \_branches
                    \_projB
                               \_trunk
                               \_tags
                               \_branches
Is that recommended or is there a smarter way to do that?
Is there any documentation regarding releasing module builds?

Thanks
Stefan


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to