On Wed, Aug 4, 2010 at 3:04 PM, <[email protected]>wrote:
> Wao, you are the men! > Indeed this was a problem of configuration. I've tried without checking > force checkout and it goes right ! > Cool > > I've looked your link and well it is not clearly written that the report > will not be avaiable but it is logic. > Maybe you can write a patch for this page to have things more clear ;-) > > Thanks again > np, you're welcome > > Alexis > > -----Original Message----- > From: Emmanuel Venisse [mailto:[email protected]] > Sent: Wednesday, August 04, 2010 2:55 PM > To: [email protected] > Subject: Re: Can't see SCM and dependencies changes report > > ok, I found the "problem" > > 2010-08-04 14:20:49,494 [pool-7-thread-1] INFO > org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor - > Performing action checkout-project > 2010-08-04 14:20:49,494 [pool-7-thread-1] INFO action#checkout-project > - Checking out project: 'mrteGest', id: '24' to 'C:\Program > Files\apache-continuum-1.3.6\data\working-directory\24'. > 2010-08-04 14:20:49,572 [pool-7-thread-1] INFO > org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: cmd.exe /X > /C "svn --non-interactive checkout file:///C:/temp/svn_repository_collab > 24" > > For your build, you run a checkout instead of an update. If it isn't the > first build, I assume you use the "fresh build" option for your build > definition [1]. With a checkout, Continuum doesn't populate scm changes > because it doesn't have a reference to use to find changes. > > Except for some cases, I consider the usage of this option as a bad > practice. Your build will be more fluent without it and Continuum will > build your projects only if it find changes in them, not all the time. > > [1] > http://continuum.apache.org/docs/1.3.6/user_guides/managing_builddef/bui > lddefGroup.html > >
