[jira] Commented: (MNG-1978) "Provided" scope transitive dependencies required + exclude dependencies for runtime scope only

["David Boden (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-1978?page=comments#action_60863 ] 

David Boden commented on MNG-1978:
----------------------------------

> If it can't be assumed to be provided transitively, then shouldn't it be treated as if it's compile scope for the transitive case?
Completely agree with this statement.

>why is this listed under the documentation-faqs component? isn't this a question about scope-handling, something that should be assigned to something like the core module (if that still exists)?
In my original comment I stated *if* there was a good explaination then please assign this to the documentation subproject. There *isn't* a good explaination. We need a code change.

"provided" dependencies should be transitive. Please move this into the relevant development subproject. Many thanks.

> "Provided" scope transitive dependencies required + exclude dependencies for runtime scope only
> -----------------------------------------------------------------------------------------------
>
>          Key: MNG-1978
>          URL: http://jira.codehaus.org/browse/MNG-1978
>      Project: Maven 2
>         Type: New Feature

>   Components: Documentation: Faqs
>     Versions: 2.0.2
>     Reporter: David Boden
>      Fix For: documentation

>
>
> Why are provided scope dependencies not transitive?
> I have several examples in my project where I need to declare a dependency as on the compilation classpath but not on the runtime classpath and I need it to be transitive. I don't want the dependency to be packaged up in my deployment artifact but my entire multi-project hierarchy relies on the dependency.
> At the moment, I have to workaround the problem, mostly by declaring duplicate provided scope dependencies in multiple projects.
> If there's a well-known answer to this query then apologies, could it be placed in the "Introduction to Dependency Mechanism" documentation.
> I would also be able to model my dependency structure more accurately if I could <exclude/> a dependency from the runtime classpath only and keep it in the compile classpath.
> E.g. 
>     <dependencies>
>         <dependency>
>             <groupId>SalesStation</groupId>
>             <artifactId>cds_ss_shared</artifactId>
>             <version>SNAPSHOT</version>
>             <exclusions>
>                 <exclusion>
>                     <groupId>SalesStation</groupId>
>                     <artifactId>ss_base_shared</artifactId>
>                     <!-- I want to be able to do this: -->
>                     <scope>runtime</scope> <!-- Exclude from runtime classpath only, not compile classpath -->
>                 </exclusion>
>             </exclusions>
>         </dependency>
>     </dependencies>

-- 
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