On Wed, 19 Apr 2006, Gunzenreiner Simon wrote: - Drop the <scope>compile</scope> - it's the default anyway, and not needed for compilation of the ear
- the modules section is only needed for modules that need special configuration, like a war module usually gets a contextRoot - do you provide your own application.xml somewhere or do you use the GenerateApplicationXmlMojo? - Did you specify the configuration at the global level or in executions? If you could paste your plugin configuration in the mail, that would be helpful. -- Kenney > I am trying to create an ear by assembling multiple other projects in Maven > 2.0.4. My ear config files are located in a separate project with > <packaging>ear</packaging>. All dependent projects are listed as <dependency> > with scope <scope>compile</scope>. In addition, I added the <modules> > configuration as described here: > http://maven.apache.org/plugins/maven-ear-plugin/howto.html. > > I am facing two problems now: > - I get an Error message if I add my EJB project to the <modules> list: > Artifact[myGroupId:sample-ejb:ejb] is not a dependency of the project. > although I added this project to the dependency list as well as to the > module list. > - Java (client) modules are not added to the generated application.xml > > Any hints really appreciated. > > Thanks > Simon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
