On Thu, Sep 30, 2010 at 7:34 AM, Nathaniel Auvil <[email protected]> wrote: > what does not make sense to you? > > If i only have a bug in the child-web project, i should not have to release > a new version of my child-service and child-core...those did not change. > This is fundemental to multi-module projects and i do not see how maven can > not support this. Releasing all modules of a project at the same time does > not make sense in this case.
If you expect this to happen often, then I agree with the advice you're getting that perhaps this module should be managed separately. If it's a one-off patch that you need to get out quickly then: 1. change the <parent><version> in the child to the prior released version of the parent 2. go into the child and release:prepare, release:perform 2a. when prompted, add an extra section to the version -- say you released 2.0, and the project now sits at 2.1-SNAPSHOT. So you release 2.0.1 of the child and set the version back to 2.1-SNAPSHOT after the release. 3. put the <parent><version> in the child back to the correct value There is an argument to release it all together, which is that you know it has all been built and tested together. If you start releasing the modules separately, then you will have to do additional testing and keep a compatibility matrix of which bits work together. You'll notice that most open source projects just release the entire thing even if only a few modules have changed -- it's less work overall. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
