My experience is that with a multi-module project, you should do as
advised here by Emmanuel delete all but the parent project builds, and
remove --non-recursive from the parent project.
Under the default scenario, where continuum tries to build each module
separately, it doesn't seem like th
On 7/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Actually, continuum create one project by module and it checkout each module in
its own directory.
If you don't want one project by module, you can delete all modules in
continuum interface and
remove --non-recursive from the build definit
Actually, continuum create one project by module and it checkout each module in
its own directory.
If you don't want one project by module, you can delete all modules in continuum interface and
remove --non-recursive from the build definition of your parent project.
Emmanuel
Jeff Mutonho a é
My top level pom defines the following modules :
eportal-services
eportal-messaging
eportal-messaging-support
eportal-webservices
eportal
Besides the failed build i mentioned in my previous post ,Continuum is
checking these out of CVS into a one directory , eg 50 , then it
cre
