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.
Right now i have separate projects for each module, but it is painful to do builds and releases. Another issue with multi-module projects is how they have to live in SVN...if you want to tag or branch, you have to tag or branch the entire codebase, not just a single module. On Thu, Sep 30, 2010 at 3:40 AM, Antonio Petrelli < [email protected]> wrote: > 2010/9/29 Nathaniel Auvil <[email protected]>: > > Some days later there is a bug in the child-web project. What i _want_ > is... > > > > parent (1.1) > > child-core (1.0) > > child-service (1.0) > > child-web (1.1) > > > > how can i do this with maven? > > Sorry but this does not make sense: either you use separated projects, > or a project-module structure. > Nothing prevents you to separate the child-web module into an > independent project. > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
