I think this last comment misses the point: I might have transitive 
dependencies* at compile-time that are not referenced anywhere in my own 
code.

And for exactly that reason I think any compile-time dependency should be 
transitive.

Best regards,
Patrick

* not talking about Maven dependencies here, but dependencies in a literal 
sense



From:
Wayne Fay <[email protected]>
To:
Maven Users List <[email protected]>, 
Date:
14.03.2013 18:25
Subject:
Re: Provided scope dependencies



> I know this is not a new issue in any way; there is a 7 year old Jira 
[2],
> which has some discussion, but seems to have no conclusion in any way 
and
> is not scheduled to be fixed.

Personally I think David Boden's latest comment in that Jira sums
things up rather nicely:
David Boden added a comment - 08/Aug/12 9:39 AM
For what it's worth, I no longer agree with this issue that I started
6 years ago! I have a best-practice document which I apply to my
projects and have pasted here in this comment. Under this strategy, I
always declare compile-time dependencies in any project that has an
import; statement referring to the class. I don't rely on transitive
dependencies when I'm actually using a dependency for compilation. I
think this is what the Maven authors intended, which is why "provided"
has stayed like it is for such a long time.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]




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

Reply via email to