I use the eclipse:eclipse goal to generate an
Eclipse Project environment. The deployment works fine. The goal creates the var classpath entries for all needed dependencies.
With m2eclipse there was the Maven Container which defines an export folder which was WEB-INF/lib for me. But i don't want to rely on m2eclipse so i don't use it anymore.
the class path entries which are generated by eclipse:eclipse goal don't have such a export folder.
While booting the servlet container with WTP it publishes all resources and classes except the libraries to the context.
Whats missing to publish the needed libs, or isn't that possible without m2eclipse integration?
Enviroment
Eclipse 3.5 JEE Galileo
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_14
m2eclipse
The maven-eclipse-plugin configuration
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.8</version>
<configuration>
<projectNameTemplate>someproject-[artifactId]</projectNameTemplate>
<useProjectReferences>false</useProjectReferences>
<downloadSources>false</downloadSources>
<downloadJavadocs>false</downloadJavadocs>
<wtpmanifest>true</wtpmanifest>
<wtpversion>2.0</wtpversion>
<wtpapplicationxml>true</wtpapplicationxml>
<wtpContextName>someproject-[artifactId]</wtpContextName>
<additionalProjectFacets>
<jst.web>2.3</jst.web>
</additionalProjectFacets>
</configuration>
</plugin>
The generated files
After executing the eclipse:eclipse goal, the dependent-module is not listed in my generated .settings/org.
eclipse.wst.common.component, so on server booting i miss the depdencies.
This is what i get:
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="someproject-core">
<wb-resource deploy-path="/" source-path="src/main/java"/>
<wb-resource deploy-path="/" source-path="src/main/webapp"/>
<wb-resource deploy-path="/" source-path="src/main/resources"/>
</wb-module>
</project-modules>
Update for upcoming readers
The problem here was the deviant packaging-type, if u use maven-eclipse-plugin please validate the use of <packaging>war</packaging> or ear.
The following problems are marked of the situations that i have two build-lifecycles in one maven pom.
