maybe setup each child as a different project group...
another way to do this would be to have that parent pom not have the children defined as modules in it... jesse On 5/11/07, alexsil <[EMAIL PROTECTED]> wrote:
Hi Erik, thank you for your answer. The structure of the project is OK (as you thought). Your workaround doesn't work. Continuum check out all at the next update. You have right, my use case is strange. I know, but I' m trying to solve another problem. The project is developed from 2 distinct groups then I want send e-mail (in case of build error) only to appropriate group, not to all. Then I set up in Continumm the Parent Project, the project A and Project B where in poms of the two projects I set different e-mail address. I'm not interested to build all from parent pom. I use this only to deploy on maven repository change of pom. Regards Alex Erik Drolshammer-2 wrote: > > alexsil wrote: >> Hi, >> If I remove "--non-recursive" option then all projects are compiled ed >> all >> projects are updated, that is the opposite that I want. In fact I want >> checkout only the parent pom and deploy only the parent pom. > > You have one project for each pom.xml in your Continuum instance, right? > (E.g. parentProject, subModuleA, subModuleB etc.) > > Have you tried to just delete all projects from Continuum except the > parent project? > > I must say your use case is strange though ;) > > -- > Regards > Erik Drolshammer > > -- View this message in context: http://www.nabble.com/Problem-with-parent-Pom-tf3726547.html#a10433254 Sent from the Continuum - Users mailing list archive at Nabble.com.
-- jesse mcconnell [EMAIL PROTECTED]
