Re: Modules Best Practices
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 -Dan On 4/25/06, Ryan Wynn <[EMAIL PROTECTED]> wrote: > > On 4/24/06, dan tran <[EMAIL PROTECTED]> 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. >
Re: Modules Best Practices
On 4/24/06, dan tran <[EMAIL PROTECTED]> 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.
Re: Modules Best Practices
I mean the scm url that makes continuum to fetch the directry tree that contains the parent and the modules directories -D On 4/24/06, Ryan Wynn <[EMAIL PROTECTED]> wrote: > > On 4/24/06, dan tran <[EMAIL PROTECTED]> wrote: > > create shell project with scm url points to the directory containing > your > > parent + the 2 children modules > > > > Then create a build definition : > > > >command: mvn > >arguramtent -f parent/pom.xml install ( what ever goal you like) > > > > -Dan > > > > That's an interesting fix. When you say point the scm url to the > directory containing the projects, what do you mean? I thought an scm > url needs to point to a particular cvs/subversion/etc project? Can you > show me an example? Do I need to use the file system scm url? Also, > should I point it to the continuum working-directory? > > Thanks, > Ryan >
Re: Modules Best Practices
On 4/24/06, dan tran <[EMAIL PROTECTED]> wrote: > create shell project with scm url points to the directory containing your > parent + the 2 children modules > > Then create a build definition : > >command: mvn >arguramtent -f parent/pom.xml install ( what ever goal you like) > > -Dan > That's an interesting fix. When you say point the scm url to the directory containing the projects, what do you mean? I thought an scm url needs to point to a particular cvs/subversion/etc project? Can you show me an example? Do I need to use the file system scm url? Also, should I point it to the continuum working-directory? Thanks, Ryan
