From users-return-6612-apmail-continuum-users-archive=continuum.apache.org@continuum.apache.org Wed Jun 18 17:04:17 2008 Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 45409 invoked from network); 18 Jun 2008 17:04:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Jun 2008 17:04:17 -0000 Received: (qmail 45423 invoked by uid 500); 18 Jun 2008 17:04:17 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 45395 invoked by uid 500); 18 Jun 2008 17:04:17 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Received: (qmail 45383 invoked by uid 99); 18 Jun 2008 17:04:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2008 10:04:17 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.206.71.24] (HELO mail2.effigie.fr) (83.206.71.24) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2008 17:03:25 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: RE : Double builds - defect CONTINUUM-1747 Date: Wed, 18 Jun 2008 19:03:25 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Double builds - defect CONTINUUM-1747 Thread-Index: AcjRYcZvouHLd91CR22wQ+5L/m78MAAAcrtQ From: "JAIGU Yann" To: X-OriginalArrivalTime: 18 Jun 2008 17:03:25.0964 (UTC) FILETIME=[391504C0:01C8D165] Content-Type: text/plain; charset="iso-8859-1" X-Virus-Checked: Checked by ClamAV on apache.org Thanks for your reply=2E=0D=0A=0D=0AYes, I did all these steps=2E=0D=0A=0D= =0AIn fact, I've just solved the problem: continuum can't resolve an artifa= ct (the parent POM in RELEASE version), although it was in the repository w= ith correct metadata and release information=2E=0D=0A=0D=0AIn the code:=0D= =0A- in class "DefaultMavenBuilderHelper", the method "getSettings" try to = load $HOME/=2Em2/settings=2Exml, even if it's missing=2E=0D=0A- when a buil= d is fired, the "DefaultMavenBuilderHelper=2EgetMavenProject()" looks up in= $HOME/=2Em2/repository and fails to resolve the parent artifact=2E=0D=0A= =0D=0A=3D> As a workaround, I've just copied the Maven's settings file to $= HOME/=2Em2 directory and it solves these problems=2E=0D=0A=0D=0AYann=0D=0A= =0D=0A=0D=0A-----Message d'origine-----=0D=0ADe : Emmanuel Venisse [mailto:= emmanuel=2Evenisse@gmail=2Ecom] =0D=0AEnvoy=E9 : mercredi 18 juin 2008 18:3= 8=0D=0A=C0 : users@continuum=2Eapache=2Eorg=0D=0AObjet : Re: Double builds = - defect CONTINUUM-1747=0D=0A=0D=0A=0D=0ADo you have added your parent proj= ect in Continuum?=0D=0ADo you have added the parent project in a remote rep= ository?=0D=0ADo you have define scm url in your projects or only in the pa= rent?=0D=0A=0D=0AEmmanuel=0D=0A=0D=0AOn Wed, Jun 18, 2008 at 3:39 PM, JAIGU= Yann wrote:=0D=0A=0D=0A> Hi all,=0D=0A>=0D=0A> We're= using continuum 1=2E1 with Maven 2=2E0=2E9 on a Windows 2003 Server =0D=0A= > box since january=2E Since 2 weeks, we have the problem described in the = =0D=0A> following defect: http://jira=2Ecodehaus=2Eorg/browse/CONTINUUM-174= 7=2E=0D=0A> It never happened before=2E=0D=0A>=0D=0A> The first build fails= with the following stacktrace:=0D=0A> org=2Ecodehaus=2Eplexus=2Etaskqueue= =2Eexecution=2ETaskExecutionException: Error =0D=0A> executing action 'upda= te-project-from-working-directory'=0D=0A> at =0D=0A> org=2Eapache=2E= maven=2Econtinuum=2Ebuildcontroller=2EDefaultBuildController=2Eperf=0D=0A> = or=0D=0A> mAction(DefaultBuildController=2Ejava:434)=0D=0A> at=0D=0A= > org=2Eapache=2Emaven=2Econtinuum=2Ebuildcontroller=2EDefaultBuildControll= er=2Ebuild(=0D=0A> DefaultBuildController=2Ejava:139)=0D=0A> at=0D= =0A> org=2Eapache=2Emaven=2Econtinuum=2Ebuildcontroller=2EBuildProjectTaskE= xecutor=2Eexec=0D=0A> uteTask(BuildProjectTaskExecutor=2Ejava:50)=0D=0A> = at=0D=0A> org=2Ecodehaus=2Eplexus=2Etaskqueue=2Eexecution=2EThreadedTa= skQueueExecutor$Execut=0D=0A> orRunnable$1=2Erun(ThreadedTaskQueueExecutor= =2Ejava:116)=0D=0A> at=0D=0A> edu=2Eemory=2Emathcs=2Ebackport=2Ejava= =2Eutil=2Econcurrent=2EExecutors$RunnableAdapter=0D=0A> =2Ecall(Executors= =2Ejava:442)=0D=0A> at=0D=0A> edu=2Eemory=2Emathcs=2Ebackport=2Ejava= =2Eutil=2Econcurrent=2EFutureTask=2Erun(FutureTask=0D=0A> =2Ejava:176)=0D= =0A> at=0D=0A> edu=2Eemory=2Emathcs=2Ebackport=2Ejava=2Eutil=2Econcu= rrent=2EThreadPoolExecutor$Worker=0D=0A> =2ErunTask(ThreadPoolExecutor=2Eja= va:665)=0D=0A> at=0D=0A> edu=2Eemory=2Emathcs=2Ebackport=2Ejava=2Eut= il=2Econcurrent=2EThreadPoolExecutor$Worker=0D=0A> =2Erun(ThreadPoolExecuto= r=2Ejava:690)=0D=0A> at java=2Elang=2EThread=2Erun(Thread=2Ejava:595= )=0D=0A> Caused by:=0D=0A> org=2Eapache=2Emaven=2Econtinuum=2Eexecution=2EC= ontinuumBuildExecutorException:=0D=0A> Error while mapping metadata:add=2Ep= roject=2Eartifact=2Enot=2Efound=2Eerror=0D=0A> add=2Eproject=2Eunknown=2Eer= ror=0D=0A>=0D=0A> at =0D=0A> org=2Eapache=2Emaven=2Econtinuum=2Eexec= ution=2Emaven=2Em2=2EMavenTwoBuildExecutor=2Eup=0D=0A> da=0D=0A> teProjectF= romCheckOut(MavenTwoBuildExecutor=2Ejava:157)=0D=0A> at=0D=0A> org= =2Eapache=2Emaven=2Econtinuum=2Ecore=2Eaction=2EUpdateProjectFromWorkingDir= ectory=0D=0A> ContinuumAction=2Eexecute(UpdateProjectFromWorkingDirectoryCo= ntinuumAction=0D=0A> =2Ejava:75)=0D=0A> at=0D=0A> org=2Eapache=2Emav= en=2Econtinuum=2Ebuildcontroller=2EDefaultBuildController=2Eperfor=0D=0A> m= Action(DefaultBuildController=2Ejava:408)=0D=0A> =2E=2E=2E 8 more=0D= =0A>=0D=0A> The second build works as usual=2E=0D=0A>=0D=0A>=0D=0A> This pr= oblem occurs for every builds since I added a parent POM to all =0D=0A> exi= sting projects=2E Additionnaly, when continuum builds a project, its =0D=0A= > version number is not correctly fetched and the previous one is =0D=0A> d= isplayed instead=2E=0D=0A>=0D=0A>=0D=0A> Is there a known workaround to the= se 2 bugs?=0D=0A> Is there a way to enable debug output, in order to find t= he original =0D=0A> problem?=0D=0A>=0D=0A> Thanks in advance=2E=0D=0A>=0D= =0A> Yann=0D=0A>=0D=0A-----------------------------------------=0D=0ALe pr= =E9sent message (y compris tous les =E9l=E9ments attach=E9s) est=0Aconfiden= tiel et destin=E9 aux seules personnes qu'il vise=2E Si vous=0Al'avez re=E7= u par erreur, merci de l'indiquer =E0 son exp=E9diteur par=0Aretour et de p= roc=E9der =E0 sa destruction dans vos syst=E8mes=2E Toute=0Autilisation ou = diffusion non autoris=E9e de son contenu, dans sa=0Atotalit=E9 ou en partie= , est strictement interdite=2E Merci de noter=0Aque les e-mails sont suscep= tibles d'=EAtre alt=E9r=E9s=2E EFFIGIE ne=0Asaurait =EAtre tenu pour respon= sable ni de la transmission erron=E9e ou=0Aincompl=E8te des informations co= ntenues dans ce message, ni des=0Ad=E9lais de r=E9ception ou des dommages = caus=E9s =E0 votre syst=E8me=2E EFFIGIE=0Ane garantit ni que l'int=E9grit= =E9 de la communication ait =E9t=E9=0Amaintenue ni que cette transmission s= oit exempte de virus,=0Ad'interceptions ou d'interf=E9rences=2E=0D=0A