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.updateProjectFromCheckOut()
shows it has a similarly hard-coded POM filename as
org.apache.maven.continuum.execution.maven.m1.MavenOneBuildExecutor.updateProjectFromCheckOut()
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 <[EMAIL PROTECTED]>:
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
