Say I have two projects, `A` and `B`.
A's dependencies are declared like this:
dependencies {
provided files('libs/foo.jar')
}
B depends on A,
dependencies {
compile project(':A')
}
Since A has a `provided` dependency on `foo.jar`, I would expect `foo.jar`
to NOT be available at runtime for project B (unless explicitly specified).
This is not the behaviour I am seeing, and project B will actually have the
class files in `foo.jar` available at runtime.
(You can see a working sample here
- https://github.com/segmentio/analytics-android. Our `core` project
declares some JARs as dependencies with a provided scope, but the
`sample-app` depending on `core` sees those JARs at runtime).
On more testing, when I upload project A as a library to Maven, and then
have another project (say C) depend on project A as a Maven dependency,
`foo.jar` is not available to project C. I think is the right behaviour,
but different from above. Shouldn't the behaviour be consistent for both of
these cases?
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
