I have got a project structure in which I have a number of child modules being built from the top level pom and the default goal is install
I was wondering how does the release plugin supposed to work, should I add the release plugin to the top level pom and just call the release:perform in this top level pom file, in which case it checks all the code out to a target – checkout subdirectory and then would it call the install goal on the checked-out code or on the existing code which is in child directories. +- pom.xml <- Add release tasks here ? +- my-app | +- pom.xml | +- src | +- main | +- java +- my-webapp | +- pom.xml | +- src | +- main | +- webapp +- checkout +- pom.xml | +- my-app | +- pom.xml | +- src | +- main | +- java | +- my-webapp | +- pom.xml | +- src | +- main | +- webapp Or should I create a new “release only” pom kept at one folder level up from the project parent pom. pom.xml <- Add release tasks here ? +- pom.xml +- my-app | +- pom.xml | +- src | +- main | +- java +- my-webapp | +- pom.xml | +- src | +- main | +- webapp +- checkout +- pom.xml | +- my-app | +- pom.xml | +- src | +- main | +- java | +- my-webapp | +- pom.xml | +- src | +- main | +- webapp Please advise. -- View this message in context: http://www.nabble.com/How-to-invoke-the-MVN-Release-plugin-for-multiple-modules-tp18525194p18525194.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]
