Compile dependencies published to maven as runtime scope

plugins
not-a-bug

(Jesse Shaffer) #1

Gradle Version: unknown, but seemingly any version?
Operating System: any
Is this a regression? not that i’m aware

Example project: http://github.com/netflix/eureka

I am trying to incorporate the eureka-client into a maven project. All netflix libraries are built with gradle, and then published to maven. However, apparently due to issues in gradle’s maven publishing plugin, all the “compile” dependencies are actually published as “runtime”, preventing maven from compiling my project (except when inside Eclipse, oddly). I cannot express just how frustrating this is and how negative an impression this has left me with, because now I have to inspect their entire dependency tree for any library I want to use, and manually add every stupid dependency to my pom. That is a complete waste of my time.

References:

  1. Gradle-generated pom.xml marks all dependencies as runtime
  2. Maven-publish plugin generated pom making dependency scope runtime
  3. https://github.com/Netflix/eureka/issues/826
  4. https://github.com/ReactiveX/RxNetty/issues/292