continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "JAIGU Yann" <yja...@effigie.fr>
Subject RE : Double builds - defect CONTINUUM-1747
Date Wed, 18 Jun 2008 17:03:25 GMT
Thanks for your reply.

Yes, I did all these steps.

In fact, I've just solved the problem: continuum can't resolve an artifact (the parent POM
in RELEASE version), although it was in the repository with correct metadata and release information.

In the code:
- in class "DefaultMavenBuilderHelper", the method "getSettings" try to load $HOME/.m2/settings.xml,
even if it's missing.
- when a build is fired, the "DefaultMavenBuilderHelper.getMavenProject()" looks up in $HOME/.m2/repository
and fails to resolve the parent artifact.

=> As a workaround, I've just copied the Maven's settings file to $HOME/.m2 directory and
it solves these problems.

Yann


-----Message d'origine-----
De : Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com] 
Envoyé : mercredi 18 juin 2008 18:38
À : users@continuum.apache.org
Objet : Re: Double builds - defect CONTINUUM-1747


Do you have added your parent project in Continuum?
Do you have added the parent project in a remote repository?
Do you have define scm url in your projects or only in the parent?

Emmanuel

On Wed, Jun 18, 2008 at 3:39 PM, JAIGU Yann <yjaigu@effigie.fr> wrote:

> Hi all,
>
> We're using continuum 1.1 with Maven 2.0.9 on a Windows 2003 Server 
> box since january. Since 2 weeks, we have the problem described in the 
> following defect: http://jira.codehaus.org/browse/CONTINUUM-1747.
> It never happened before.
>
> The first build fails with the following stacktrace:
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error 
> executing action 'update-project-from-working-directory'
>        at 
> org.apache.maven.continuum.buildcontroller.DefaultBuildController.perf
> or
> mAction(DefaultBuildController.java:434)
>        at
> org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(
> DefaultBuildController.java:139)
>        at
> org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec
> uteTask(BuildProjectTaskExecutor.java:50)
>        at
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut
> orRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
>        at
> edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter
> .call(Executors.java:442)
>        at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask
> .java:176)
>        at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
> .runTask(ThreadPoolExecutor.java:665)
>        at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
> .run(ThreadPoolExecutor.java:690)
>        at java.lang.Thread.run(Thread.java:595)
> Caused by:
> org.apache.maven.continuum.execution.ContinuumBuildExecutorException:
> Error while mapping metadata:add.project.artifact.not.found.error
> add.project.unknown.error
>
>        at 
> org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.up
> da
> teProjectFromCheckOut(MavenTwoBuildExecutor.java:157)
>        at
> org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory
> ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction
> .java:75)
>        at
> org.apache.maven.continuum.buildcontroller.DefaultBuildController.perfor
> mAction(DefaultBuildController.java:408)
>        ... 8 more
>
> The second build works as usual.
>
>
> This problem occurs for every builds since I added a parent POM to all 
> existing projects. Additionnaly, when continuum builds a project, its 
> version number is not correctly fetched and the previous one is 
> displayed instead.
>
>
> Is there a known workaround to these 2 bugs?
> Is there a way to enable debug output, in order to find the original 
> problem?
>
> Thanks in advance.
>
> Yann
>
-----------------------------------------
Le présent message (y compris tous les éléments attachés) est
confidentiel et destiné aux seules personnes qu'il vise. Si vous
l'avez reçu par erreur, merci de l'indiquer à son expéditeur par
retour et de procéder à sa destruction dans vos systèmes. Toute
utilisation ou diffusion non autorisée de son contenu, dans sa
totalité ou en partie, est strictement interdite. Merci de noter
que les e-mails sont susceptibles d'être altérés. EFFIGIE ne
saurait être tenu pour responsable ni de la transmission erronée ou
incomplète des informations contenues dans ce message,  ni des
délais de réception ou des dommages causés à votre système. EFFIGIE
ne garantit ni que l'intégrité de la communication ait été
maintenue ni que cette transmission soit exempte de virus,
d'interceptions ou d'interférences.


Mime
View raw message