Thomas Broyer wrote at some time: > Because a class in A transitively depends on a class provided by C then it > *has* to know about C. Class hierarchy is part of the API (which is one > reason you should generally prefer composition over inheritance).
The compiler needs to know about artifact C of course. But I as the consumer of artifact B should not need to know B's dependencies. Actually I thought this was the reason for the whole automatic resolution of transitive dependencies. This is not for convenience, it hides internal details of B from A. Otherwise that would mean I would need to first look at the POMs of all my dependencies and basically copy all provided scope dependencies to my project. Which kind of reminds me of software development without Maven. Best regards, Patrick -------------------------------------------------------------------------------------------------------------------------------------------- Patrick Schlebusch - KISTERS AG - Charlottenburger Allee 5 - 52068 Aachen - Germany Handelsregister Aachen, HRB-Nr. 7838 | Vorstand: Klaus Kisters, Hanns Kisters | Aufsichtsratsvorsitzender: Dr. Thomas Klevers Tel.: +49 241 9671 -466 | Fax: +49 241 9671 -555 | E-Mail: [email protected] | WWW: http://www.kisters.de -------------------------------------------------------------------------------------------------------------------------------------------- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
