continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dan tran" <>
Subject Re: Modules Best Practices
Date Tue, 25 Apr 2006 13:59:13 GMT
hi Ryan

What you did also works.  Basically, you use file url to import multiple
projects into contiuum.
after that continuum, continuum uses scm url in each indiviual module to
fetch the source.

What i shown you is just import single project and have continuum to do the
build just like you
do it from command line to use the parent pom to build muliple modules


On 4/25/06, Ryan Wynn <> wrote:
> On 4/24/06, dan tran <> wrote:
> > I mean the scm url that makes continuum to fetch the directry tree that
> > contains the parent and the modules directories
> >
> > -D
> >
> Okay, I that is working now.  I used the file system scm url and
> pointed to the directory containing all the projects.  This directory
> was obtained using cvs export of all my projects.  In the past I had
> just uploaded the pom for a project, but I guess this doesn't work for
> projects with modules.  That is why I used the cvs export and point to
> url approach.
> So, if I understand this correctly Continuum just needs a url to
> initially import the projects.  After that Continuum will use the scm
> in the pom to get updates and never look at the initial url used to
> load the project?  That seems correct to me I just wanted to make sure
> I understand it correctly.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message