Maven2 Multiple Module Projects - Flat Layout

[GoogleCodeExporter]

I'm using vulcan-web-0.9.200.400.war, 
OS Red Hat Enterprise Linux ES release 4 (Nahant Update 5)

I'm trying to use vulcan on projects with Maven2 Multiple Module Projects -
Flat Layout structure, and it fails.

I used the same pom.xml (only changing path for modules, adding or removing
".." before module path/name) in both structures, flat and hierarchical.
Hierarchical works fine. Flat fails in different ways.

First: Import
Shows the error message "The specified URL is not recognized by any
Repository Plugins."

Second: Build
I tryed only importing the parent and then build it.
build log says

Reason: Could not find the model file
'/product/vulcan/work/parent/../module1/pom.xml'. for project unknown

[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Could not find the model
file '/product/vulcan/work/parent/../module1/pom.xml'. for project unknown
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:376)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:289)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Could not
find the model file '/product/vulcan/work/parent/../module1/pom.xml'. for
project unknown
    at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjec
tBuilder.java:1381)
    at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(
DefaultMavenProjectBuilder.java:474)
    at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBui
lder.java:197)
    at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:548)
    at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:458)
    at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:524)
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:362)
    ... 11 more
Caused by: java.io.FileNotFoundException:
/product/vulcan/work/parent/../module1/pom.xml (No such file or directory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:106)
    at hidden.org.codehaus.plexus.util.xml.XmlReader.<init>(XmlReader.java:123)
    at
hidden.org.codehaus.plexus.util.xml.XmlStreamReader.<init>(XmlStreamReader.java:
67)
    at
hidden.org.codehaus.plexus.util.ReaderFactory.newXmlReader(ReaderFactory.java:11
3)
    at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjec
tBuilder.java:1376)
    ... 17 more

Original issue reported on code.google.com by juangar...@gmail.com on 25 Jan 2008 at 2:06

[GoogleCodeExporter]

Original comment by chris.eldredge@gmail.com on 25 Jan 2008 at 3:02

• Changed state: Accepted
• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

Committed a fix in r528, build 287.

http://vulcan-project.org/live/viewProjectStatus.do?transform=xhtml&projectName=
vulcan&buildNumber=287

Since I'm not aware of any public projects that use a nested parent pom, I 
can't test
this for real very easily.  However, the new unit tests are passing so hopefully
that's good enough.

If you'd like to try this new build, you can download the snapshot here:

http://www.vulcan-project.org/live/site/vulcan/vulcan-web/target/vulcan-web-0.9-
SNAPSHOT.war

Be advised though that this build changes the persistence layer from the 
previous
release.  It will attempt to convert your existing build outcomes to the new 
storage
layer.

Original comment by chris.eldredge@gmail.com on 25 Jan 2008 at 5:22

• Changed state: Fixed