On Mon, Sep 17, 2012 at 8:48 PM, Paul Vonnahme
<vonnahme@xxxxxxxxx> wrote:
If I create a non-maven ear project, and add an external library to
the ear specifying the deploy directory as /lib, I get an entry in
org.eclipse.wst.common.component that looks like this:
<dependent-module archiveName="log4j-1.2.14.jar"
deploy-path="/lib"
handle="module:/classpath/lib/C:/Users/.../log4j/log4j/1.2.14/log4j-1.2.14.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
If I have a maven project and I add a dependency to the ear, I get:
<dependent-module archiveName="log4j-1.2.14.jar"
deploy-path="/"
handle="module:/classpath/var/M2_REPO/log4j/log4j/1.2.14/log4j-1.2.14.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
Notice the 'deploy-path' is "/" instead of "/lib". I have my ear pom
set up with:
<plugin>
<artifactId>maven-ear-plugin</artifactId>
<configuration>
...
<defaultJavaBundleDir>lib/</defaultJavaBundleDir>
<version>5</version>
</configuration>
</plugin>
Is there something I'm missing, or is there a reason it works this way?
Thanks,
Paul
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users