It's not good you use all the 150 project in a large project. some of the project should be idependent project if it don't have much real relative to other project. other project use <dependeces> to dependon it.
if you have a branch project should under bugfix developement. for example the last version is 1.1, now the new developing version should 1.2-SNAPSHOT. after you finish you development, you modified all the pom.xml which dependent on the fixed version. 2008/10/6 Stefan Fritz <[EMAIL PROTECTED]> > Hi, > > We use Maven in an environment where we have ca. 150 projects. > One project is the toplevel project (= the final deliverable to the > customer/user). > This project has dependencies to 10 projects, which have dependencies to > other projects etc. In the end we have 150 different projects in the > dependency hierachy. > > The challange now is what happens if in one of the projects on the lowest > level is bug. > This means we have to branch from our released version to work on a patch > and then release the patched version. > > From my understanding the only way to do that is to branch all projects > which depend on the "buggy" project. And the same has to be done for all > levels up to toplevel project. > Most low level components are referenced by multiple projects and therefore > a patch-branch would afect ca. 30 projects :-( > As you can imagine this can end up in a nightmare of manual steps and/or > scripting. > Therefore I hope anybody has a better approach to that. > > Is there a simple way to do that? > Any automation in Maven? > Any best practices? > > Thanks > Stefan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
