Circular dependency stops depednency resolution
-----------------------------------------------

                 Key: MNG-3459
                 URL: http://jira.codehaus.org/browse/MNG-3459
             Project: Maven 2
          Issue Type: Bug
    Affects Versions: 2.0.8
            Reporter: Gilles Scokart


batik:batik-bridge and batik:batik-script:jar version 1.6-1 have a circular 
dependency.  Depending where you start to depend on one of those, you will 
receive different dependencies.

For example, if I have a module with a dependency of fop, I got this 
dependencies:

[INFO] test1:testart:jar:1.0-SNAPSHOT
[INFO] \- org.apache.xmlgraphics:fop:jar:0.93:compile
[INFO]    +- org.apache.xmlgraphics:xmlgraphics-commons:jar:1.1:compile
[INFO]    +- batik:batik-svg-dom:jar:1.6-1:compile
[INFO]    |  +- batik:batik-dom:jar:1.6-1:compile
[INFO]    |  |  +- batik:batik-css:jar:1.6-1:compile
[INFO]    |  |  +- batik:batik-xml:jar:1.6-1:compile
[INFO]    |  |  \- xerces:xercesImpl:jar:2.5.0:compile
[INFO]    |  \- batik:batik-parser:jar:1.6-1:compile
[INFO]    +- batik:batik-bridge:jar:1.6-1:compile
[INFO]    |  \- batik:batik-script:jar:1.6-1:compile
[INFO]    +- batik:batik-awt-util:jar:1.6-1:compile
[INFO]    |  \- batik:batik-util:jar:1.6-1:compile
[INFO]    |     \- batik:batik-gui-util:jar:1.6-1:compile
[INFO]    +- batik:batik-gvt:jar:1.6-1:compile
[INFO]    +- batik:batik-transcoder:jar:1.6-1:compile
[INFO]    +- batik:batik-extension:jar:1.6-1:compile
[INFO]    +- batik:batik-ext:jar:1.6-1:compile
[INFO]    |  \- xml-apis:xmlParserAPIs:jar:2.0.2:compile
[INFO]    +- commons-logging:commons-logging:jar:1.0.4:compile
[INFO]    +- commons-io:commons-io:jar:1.1:compile
[INFO]    +- org.apache.avalon.framework:avalon-framework-api:jar:4.3.1:compile
[INFO]    \- org.apache.avalon.framework:avalon-framework-impl:jar:4.3.1:compile

But If I have a module with direct dependencies on batik-script, I have :

[INFO] test1:testart:jar:1.0-SNAPSHOT
[INFO] \- batik:batik-script:jar:1.6-1:compile
[INFO]    +- batik:batik-bridge:jar:1.6-1:compile
[INFO]    +- batik:batik-svg-dom:jar:1.6-1:compile
[INFO]    |  +- batik:batik-dom:jar:1.6-1:compile
[INFO]    |  |  +- batik:batik-css:jar:1.6-1:compile
[INFO]    |  |  +- batik:batik-xml:jar:1.6-1:compile
[INFO]    |  |  \- xerces:xercesImpl:jar:2.5.0:compile
[INFO]    |  \- batik:batik-parser:jar:1.6-1:compile
[INFO]    +- batik:batik-gvt:jar:1.6-1:compile
[INFO]    |  \- batik:batik-awt-util:jar:1.6-1:compile
[INFO]    |     \- batik:batik-util:jar:1.6-1:compile
[INFO]    |        \- batik:batik-gui-util:jar:1.6-1:compile
[INFO]    |           \- batik:batik-ext:jar:1.6-1:compile
[INFO]    |              \- xml-apis:xmlParserAPIs:jar:2.0.2:compile
[INFO]    \- rhino:js:jar:1.5R4.1:compile

In the first case, the dependency rhino:js:jar is not included.  In the second, 
it is.
(See also MNG-3370 )

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