Re: Adding projects with parent poms
we use the same command line that a user. continuum call m2 command (m2 --batch-mode --non-recursive clean:clean install by default) Emmanuel Mark Hobson a écrit : Hi, It seems continuum has problems downloading parent poms when adding m2 projects. I've added the bootstrap repo to the continuum users' m2 settings.xml to avoid the chicken-and-egg problem. All builds fine from the command line but fails from within continuum. Any idea why continuum appears to be ignoring the bootstrap repo in settings.xml even though it logs that it's reading the file? Cheers, Mark
Re: Adding projects with parent poms
Actually pom project aren't add in continuum, so I think it's why continuum can install it in repo and then can't retreive it on an other project build. Emmanuel Mark Hobson a écrit : Hi, It seems continuum has problems downloading parent poms when adding m2 projects. I've added the bootstrap repo to the continuum users' m2 settings.xml to avoid the chicken-and-egg problem. All builds fine from the command line but fails from within continuum. Any idea why continuum appears to be ignoring the bootstrap repo in settings.xml even though it logs that it's reading the file? Cheers, Mark
Re: Adding projects with parent poms
On 07/10/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > Actually pom project aren't add in continuum, so I think it's why continuum > can install it > in repo and then can't retreive it on an other project build. Ah ok, so for pom projects with modules do I have to add each module separately? Mark
Re: Adding projects with parent poms
No, actually, you can add a pom project with modules, continuum will add all modules in database but not project with pom type. So continuum will build all modules but if you update your parent pom without install it manually in your repo, modules will can't be updated with parent updates Emmanuel Mark Hobson a écrit : On 07/10/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: Actually pom project aren't add in continuum, so I think it's why continuum can install it in repo and then can't retreive it on an other project build. Ah ok, so for pom projects with modules do I have to add each module separately? Mark
Re: Adding projects with parent poms
On 07/10/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > No, actually, you can add a pom project with modules, continuum will add all > modules in > database but not project with pom type. So continuum will build all modules > but if you > update your parent pom without install it manually in your repo, modules will > can't be > updated with parent updates Sorry, I don't think I'm thread-safe, thought we were talking about the module support that you said will be fixed in beta2 ;) This problem is m2 downloading parent poms from a settings.xml configured repo. m2 happily does it from the command line but not within continuum - it complains about a missing parent pom and uses the defaults, hence the build fails. If I build the project from the command line to bootstrap the parent poms into the local repo, then everything works fine. It appears m2 within continuum ignores the settings.xml? Mark
Re: Adding projects with parent poms
Mark Hobson a écrit : On 07/10/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: No, actually, you can add a pom project with modules, continuum will add all modules in database but not project with pom type. So continuum will build all modules but if you update your parent pom without install it manually in your repo, modules will can't be updated with parent updates Sorry, I don't think I'm thread-safe, thought we were talking about the module support that you said will be fixed in beta2 ;) This problem is m2 downloading parent poms from a settings.xml configured repo. m2 happily does it from the command line but not within continuum - it complains about a missing parent pom and uses the defaults, hence the build fails. If I build the project from the command line to bootstrap the parent poms into the local repo, then everything works fine. It appears m2 within continuum ignores the settings.xml? Do you have try the command I wrote in my previous mail? By default, we don't use a specific settings.xml file. I suppose you don't define the use of an other settings.xml file in your build definition. I can't reproduce your problem. Emmanuel
