Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
Understanding Compile- vs Run-time Dependencies
I understand that a dependency with the “runtime” scope will be available at runtime and not at compile time. But I don’t understand why you could want that! Why not simply use the “compile” scope instead?
The docs don’t really help. Any idea?
runtimeis useful for dependencies required for unit tests and at runtime, but not at compile time. This may typically be dynamically loaded code, such as JDBC drivers, which are not directly referenced in the program code.Setting dependency to
providedensures that there isn’t an accidental dependency on the code, and also keeps the dependency from being transitive. So that, for example, if module A has aprovideddependency on library X, and module B depends on module A, it does not inherit the dependency on library X. Using "runtime" or "compile" would cause B to depend on X.