Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Received-SPF: pass (asf.osuosl.org: domain of wim.deblauwe@gmail.com
 designates 64.233.184.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=EhgLlnTrMFVRF8tRt4xBTxP1+3rnghGqZHWKDa+24Xr4g1CPckd71LPtxeQecWAkqbL4c1DoaUVXE8CZvFrUKZRq4uG/9vdorB/t4+ABsHkCwNZmT6vh9KSyy/y4nrSJIc64RxrWAqOEVl5o/FkA5wn1B0r0Cg06PW0TlTHYiuo=
Message-ID: <c7c567b10511022318l7ef35963g@mail.gmail.com>
Date: Thu, 3 Nov 2005 08:18:39 +0100
From: Wim Deblauwe <wim.deblauwe@gmail.com>
To: continuum-users@maven.apache.org
Subject: Re: pom.xml in a build directory
In-Reply-To: <4368F3EE.7060801@denverdata.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_11631_1995155.1131002319709"
References: <c7c567b10511020429v7c8c5748n@mail.gmail.com>
	 <4368D900.1060401@denverdata.com>
	 <c7c567b10511020726k1311af45j@mail.gmail.com>
	 <4368F3EE.7060801@denverdata.com>

------=_Part_11631_1995155.1131002319709
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Alas, it does not work. I tried it and it fails with the following error:

org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error
while mapping metadata.
at
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateP=
rojectFromCheckOut
(MavenTwoBuildExecutor.java:91)
at
org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryCon=
tinuumAction.execute
(UpdateProjectFromWorkingDirectoryContinuumAction.java:59)
at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(
DefaultBuildController.java:168)
at
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.execute=
Task
(BuildProjectTaskExecutor.java:53)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorR=
unnable.run
(ThreadedTaskQueueExecutor.java:103)
at java.lang.Thread.run(Thread.java:595)
Caused by:
org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException:
Cannot build maven project from C:\Program Files\Apache Software
Foundation\continuum-
1.0\bin\win32\..\..\apps\continuum\working-directory\26\pom.xml.
at
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.get=
MavenProject
(DefaultMavenBuilderHelper.java:260)
at
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.map=
MetadataToProject
(DefaultMavenBuilderHelper.java:89)
at
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateP=
rojectFromCheckOut
(MavenTwoBuildExecutor.java:87)
... 5 more
Caused by: org.apache.maven.project.ProjectBuildingException: Could not fin=
d
the model file 'C:\Program Files\Apache Software Foundation\continuum-
1.0\bin\win32\..\..\apps\continuum\working-directory\26\pom.xml'.
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(
DefaultMavenProjectBuilder.java:1061)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(
DefaultMavenProjectBuilder.java:291)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(
DefaultMavenProjectBuilder.java:283)
at
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.get=
MavenProject
(DefaultMavenBuilderHelper.java:252)
... 7 more
Caused by: java.io.FileNotFoundException: C:\Program Files\Apache Software
Foundation\continuum-
1.0\bin\win32\..\..\apps\continuum\working-directory\26\pom.xml (The system
cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileReader.<init>(FileReader.java:55)
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(
DefaultMavenProjectBuilder.java:1056)
... 10 more


Everything is copied ok in the working directory, and I changed the pom fil=
e
in the build definition to "build/pom.xml", but it seems like continuum doe=
s
not take that into account (judging from the path that is displayed in the
file not found exception)

should this be reported as a bug?

regards,

Wim


2005/11/2, Doug Douglass <ddouglass@denverdata.com>:
>
> Wim,
>
> Your problem is similar, but...
>
> My project layout is:
>
> <root>
> + build
> ++ project.xml
> + <module1>
> ++ project.xml
> ++ src
> + <module2>
> ++ project.xml
> ++src
>
> Here's what I had done in my case:
>
> 1) Add project using the "build" POM/project.xml
>
> 2) Change the scm url in the continuum project definition to point to
> the parent module ("module-name" in your case, "<root>" in my case).
>
> 3) Change POM filename in the continuum build definition for the
> project to "build/pom.xml" ("build/project.xml" in my case ).
>
> Continuum should now properly checkout all the code in your "module-name"=
.
>
> In my case, the build then fails because I don't have a POM at the
> "module-name" level, so the issue I reported had to do with continuum
> not using the POM filename from the build definition. Your situation may
> actually succeed because you have a POM at the "module-name" level.
>
> FYI, a quick glance at
>
> org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updat=
eProjectFromCheckOut
> ()
> shows it has a similarly hard-coded POM filename as
>
> org.apache.maven.continuum.execution.maven.m1.MavenOneBuildExecutor.updat=
eProjectFromCheckOut
> ()
>
> HTH,
> Doug
>
> Wim Deblauwe wrote:
>
> >Should I open a new issue in JIRA for my problem or just comment on the
> >current one?
> >
> >2005/11/2, Doug Douglass <ddouglass@denverdata.com>:
> >
> >
> >>I reported this problem for maven 1 projects:
> >>
> >>http://jira.codehaus.org/browse/CONTINUUM-381
> >>
> >>
> >>Wim Deblauwe wrote:
> >>
> >>
> >>>Hi,
> >>>
> >>>I'm using a structure where my pom.xml is in a subdirectory called
> build
> >>>like this:
> >>>
> >>>module-name
> >>>+ build
> >>>+ pom.xml
> >>>+ src
> >>>+ ...
> >>>
> >>>Continuum seems to handle this case inproperly. In
> >>>
> >>>
> >>"working-directory\21" of
> >>
> >>
> >>>my continuum installation, only the contents of the build directory is
> >>>copied there. As a result no java files can be found to compile. I'm
> >>>
> >>>
> >>using
> >>
> >>
> >>>scm:local by the way and I also extend a parent pom. This parent pom
> >>>
> >>>
> >>gets
> >>
> >>
> >>>read, because I specify there that my reports should be in a temp
> >>>
> >>>
> >>directory
> >>
> >>
> >>>and this happens.
> >>>
> >>>Is this a known bug or am I doing something wrong?
> >>>
> >>>regards,
> >>>
> >>>Wim
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
>

------=_Part_11631_1995155.1131002319709--