What I find helped me tremendously when figuring out the best way to organise our project is to look at examples.
Large scale open source projects like the spring framework and maven itself are good places to learn. regards Brian On 30 September 2010 13:32, Antonio Petrelli <[email protected]>wrote: > 2010/9/30 Nathaniel Auvil <[email protected]>: > > 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. > > I understand the point, but its intrinsically wrong. When you fix > something inside a module you are, in fact, fixing the whole project. > Otherwise, if you want to manage those module separately, you'd better > move them in a separate project. > In fact, one main point of a multi-module project is to maintain the > versions of modules all together. > > > 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. > > You can try going in the module subdir and running the release plugin. > It *might* work, however I strongly discourage it. > > > Right now i have separate projects for each module, but it is painful to > do > > builds and releases. > > Doing as I said in the sentence before is painful in the exact same > way. It would be less painful if you tag only the main project. > > > 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. > > At this point I suppose you are managing projects in a wrong way. Why > did you put the whole codebase under a single project? > If it is only for sharing configuration, then create a separate master > pom and use it as parent for all the other projects. > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
