I'm attempting to use the m2metadata plugin on our rather complex maven
build, as a sort of transition tool. Occasionally in the maven build
there are dependencies with a "provided" scope. If I understand
correctly, these "provided" dependencies are required for compiling but
(a) wouldn't be included in an archive and (b) wouldn't be included in
the project's list of transitive dependencies. So for instance if
project A has a "provided" dependency on org.acme:superlib:1.0 and
project B has a compile dependency on project A, then
org.acme:superlib:1.0 wouldn't show up in project B's dependency graph.
Unfortunately m2metadata doesn't seem to support (b) except in the case
of war projects. I understand that this is mainly because Gradle
doesn't support the concept of "provided" dependencies
(http://issues.gradle.org/browse/GRADLE-784).
I'm trying to hack at the m2metadata plugin to fake some kind of support
for this, and am being hampered by my poor understanding of how Gradle
deals with transitive dependencies across dependent projects. So my
question is, does anyone have a suggestion on how to gain this effect in
Gradle?
-Dave
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
