Can you show us your (simplified?) pom(s)? I've tried to reproduce your problem and I had no problem at all to package the 2 nd module. And I ve tried several configuration.
May be I missed something in your configuration. -----Message d'origine----- De : Martin Höller [mailto:[EMAIL PROTECTED] Envoyé : mercredi 23 avril 2008 11:09 À : Maven Users List Objet : problems building a multimodule project with EJB3 modules Hi all! I'm having problems with a multimodule project with EJB3 dependencies. It seems maven is not able to include EJB3 modules in the classpath of other child-modules when not in the local repository. The simplest project struture to reproduce is the following: parent (packagin pom) | +-- child1 (packagin jar) | `-- child2 (packagin ejb) where child1 depends on child2. When I execute "mvn package" (with an empty local repository) from the parent child2 is packaged and then I get a missing dependency in child1 on child2: INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. Missing: ---------- 1) at.co.xss.mhtest.multimodule:child2:jar:1.0-SNAPSHOT [...] However, when I execute "mvn install" instead everything compiles and packages fine. The problem seems to be that maven is not able to include the classes of the child2 module in the classpath of child1 when it is compiling child1. When a "mvn install" is executed, the final jar is in the local repo and correctly included in the classpath, so this shows no problems. Is this behaviour with EJB3 modules intentional, am I missing something here or is this a bug? Thanks for your suggestions, - martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
