You are corect, it's because the only difference between the two
dependencies is their type, see

http://jira.codehaus.org/browse/MAVEN-1365

and it's related issues

J.




Extranet
[EMAIL PROTECTED] - 23/09/2004 13:44


Veuillez r�pondre � [EMAIL PROTECTED]

Pour : users

cc :


Objet :     possible bug with dependencies


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]










This message and any attachments (the "message") is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

                ---------------------------------------------

Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to