Thanks John, I can build the projects "xxxx-ejb" and "xxxx" now. However, mvn-install still fails for "xxxx-test", "xxxx-ear" and "xxxx-parent". Apparently, the root cause is that "xxxx-ear", which the other two depend on, doesn't compile, and that is because it has a dependency on "xxxx" with a packaging type of "war". Here's a snippet from the pom.xml of "xxxx-ear":
<dependency>
<groupId>de.xplace.myxplace</groupId>
<artifactId>myxplace3.0</artifactId>
<version>0.0.1-SNAPSHOT</version>
<type>war</type>
<scope>runtime</scope>
</dependency>
<dependency>
<artifactId>xxxx</artifactId>
<groupId>my.group</groupId>
<version>0.0.1-SNAPSHOT</version>
<type>war</type>
</dependency>
and here's a snippet from the pom of "xxxx":
<project>
...
<artifactId>xxxx</artifactId>
<groupId>my.group</groupId>
<version>0.0.1-SNAPSHOT</version>
<packaging>ear</packaging>
...
</project>
I think the problem is that xxxx-ear depends on a project with <type>war</war>, but xxxx has <packaging>ear</packaging>. I tried changing the dependency declaration to <type>ear</type>, but get the following error message:
"Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.3.1:generate-application-xml
Artifact[war:my.group:xxxx] is not a dependency of the project."
I have done some Java SE maven projects, but I'm new to web development with maven, and I haven't got a clue how to fix that.