Guys,
I might have found a bug, please let me know whether I am correct or not. I have a
maven project whose purpose is to build an EAR. For that it has dependencies over
other artifacts we generate.
Currently, I am building release 3.4.1 which contains, namely, the following modules
[...]
scheduler-3.4.1.jar
[...]
scheduler-3.4.1.war
Part of my project.xml is:
[...]
<dependency>
<groupId>bsb-jf</groupId>
<artifactId>scheduler</artifactId>
<version>3.4.1</version>
<type>ejb</type>
<properties>
<ear.bundle>true</ear.bundle>
</properties>
</dependency>
<!-- Scheduler Web Application -->
<dependency>
<groupId>bsb-jf</groupId>
<artifactId>scheduler</artifactId>
<version>3.4.1</version>
<type>war</type>
<properties>
<ear.bundle>true</ear.bundle>
<ear.appxml.war.context-root>scheduler</ear.appxml.war.context-root>
</properties>
</dependency>
[...]
WAR is never downloaded, neither included in the EAR. If I rename the file and the
dependency, everything is ok. Is is normal or a limitation (types are different in
this case so it should be OK)
Regards,
St�phane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
