maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Boden (JIRA)" <>
Subject [jira] Created: (MNG-2205) "provided" scope dependencies must be transitive
Date Thu, 06 Apr 2006 10:37:48 GMT
"provided" scope dependencies must be transitive

         Key: MNG-2205
     Project: Maven 2
        Type: Bug

  Components: Dependencies  
    Reporter: David Boden
    Priority: Critical

A provided scope dependency can also be thought of as "compile-only".

Project A requires Sybase JConnect on the runtime classpath. Project A declares a "provided"
dependency on Sybase JConnect.
Project B depends upon Project A. Project B declares a "compile" dependency on Project A.
Project C depends upon Project B. Project C declares a "compile" dependency on Project B.

| - compile dependency
| - compile dependency
| - provided dependency
Sybase JConnect

So, does Project C transitively depend on Sybase JConnect. Yes, of course! The "provided"
dependency needs to be transitive.

Ultimately, when Project C gets deployed, Sybase JConnect needs to be somewhere on the runtime
classpath in order for the application to function. It's valid for Project C to assume that
Sybase JConnect is available and use JDBC all over the Project C code. Project C is safe to
do this because it can happily deduce that Sybase JConnect will be there in the runtime environment
because Project A NEEDS IT.

I've got Use Cases all over my aggregated build which make it absolutely critical and common
sense that provided scope dependencies are transitive. For the (very rare) odd case where
you don't want to inherit provided dependencies, you can <exclude/> them.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message