-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
Hi,
we have run into a problem with building maven2 projects. The problem originates
in our repository/working copy layout, which looks like this:
sandbox/
+- build/
+- pom.xml (super-POM, referenced by project POMs) |
+- common/ (project common)
+- module1/
pom.xml (module POM) +- module2/ |
pom.xml (module POM) +- pom.xml (project-POM for common, referenced by module POMs) |
All project POMs (like common/pom.xml) reference build/pom.xml as their parent.
The build/pom.xml contains common settings like compiler settings, repositories,
etc.
The Hudson project for common checks out two modules,
- svn/common/trunk into common
- svn/build into build
resulting in a job workspace layout identical to the above shown working copy
layout. This way, the working copy layout for hudson and on the developer
machines are identical.
The root POM in the Hudson project common is set to common/pom.xml, which is the
starting point for the common project. However, when starting the build, Hudson
incorrectly resolves this to workspace/common/common/pom.xml, instead of
workspace/common/pom.xml, resulting in:
"Parsing POMs
No such file /opt/hudson/jobs/common-integration/workspace/common/common/pom.xml
Perhaps you need to specify the correct POM file path in the project configuration?
finished: FAILURE"
regards,
Karl