[ 
http://jira.codehaus.org/browse/MDEP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107898
 ] 

Brian Fox commented on MDEP-112:
--------------------------------

Ok it's more clear now. The war plugin is including the contents of the runtime 
scope. Runtime scope includes compile and transitive things. If you need 
something for compile but not for runtime, then you must mark it as provided. 
This is the difference between the two dependencies you identified above.

> Container dependency jar file get copied during the deployment or during hte 
> installation1
> ------------------------------------------------------------------------------------------
>
>                 Key: MDEP-112
>                 URL: http://jira.codehaus.org/browse/MDEP-112
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: copy-dependencies
>    Affects Versions: 2.0
>         Environment: WindowXP(CYGWIN)     JDK 1.5.0_07
>            Reporter: Alan Mehio
>            Assignee: Brian Fox
>            Priority: Trivial
>             Fix For: 2.0
>
>
> The dependency get copied even it is provided by the container 
> This happens in the following scenario :
> module A has dependecies as below 
> <dependencies>
>               <dependency>
>                       <groupId>axis</groupId>
>                       <artifactId>axis-schema</artifactId>
>                       <version>1.3</version>
>               </dependency>
>               <dependency>
>                       <groupId>axis</groupId>
>                       <artifactId>axis-wsdl4j</artifactId>
>                       <version>1.3</version>
>               </dependency>
>               <dependency>
>                       <groupId>xml-apis</groupId>
>                       <artifactId>xml-apis</artifactId>
>                       <version>1.0.b2</version>
>               </dependency>
>               <dependency>
>                       <groupId>javax.xml</groupId>
>                       <artifactId>jaxrpc-api</artifactId>
>                       <version>1.1</version>
>               </dependency>
>               <dependency>
>                       <groupId>commons-discovery</groupId>
>                       <artifactId>commons-discovery</artifactId>
>                       <version>0.2</version>
>               </dependency>
>               <dependency>
>                       <groupId>axis</groupId>
>                       <artifactId>axis-saaj</artifactId>
>                       <version>1.2</version>
>               </dependency>
>       </dependencies>
> you have module B which has the below  dependencies
> <dependencies>
>               <dependency>
>                       <groupId>mygroup</groupId>
>                       <artifactId>common</artifactId>
>                       <version>1.0.0</version>
>               </dependency>
>               <dependency>
>                       <groupId>mygroup</groupId>
>                       <artifactId>service</artifactId>
>                       <version>1.0.0</version>
>               </dependency>
>               <dependency>
>                       <groupId>mygroup</groupId>
>                       <artifactId>model</artifactId>
>                       <version>1.0.0</version>
>               </dependency>
>               <dependency>
>                       <groupId>tomcat</groupId>
>                       <artifactId>servlet-api</artifactId>
>                       <version>5.0.18</version>
>                       <scope>provided</scope>
>               </dependency>
>       </dependencies>
> The one which get copied is servlet-api-2.3.jar 
> On the otherhand, the other project is using the same dependency ( 
> servlet-api ) but the only difference is the axis artifact and its 
> dependencies are not included
> Regards,
> Alan Mehio
> London, UK

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to