geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Smith <dsm...@pivotal.io>
Subject [DISCUSS] Changing many geode-core dependencies from compile to runtime
Date Fri, 15 Mar 2019 18:53:18 GMT
Hi,

We would like to start using gradle's new implementation dependency
notation in our build files.

This will affect downstream consumers of geode-core, hopefully in a good
way, in that many of our dependencies will now be marked runtime
dependencies in the pom instead of compile. That means it is easier for
users to avoid accidentally using one of these dependencies in their code.
But it also means if they are using one of these dependencies directly,
they will have to explicitly add it to their maven/gradle build going
forward.

Here is a PR for this:
https://github.com/apache/geode/pull/3314

Are there any concerns with making this switch?

These are the dependencies that are being flipped to runtime instead of
compile in the pom:

com.github.stephenc.findbugs:findbugs-annotations
org.jgroups:jgroups
antlr:antlr
com.fasterxml.jackson.core:jackson-annotations
com.fasterxml.jackson.core:jackson-databind
commons-io:commons-io
commons-validator:commons-validator
javax.xml.bind:jaxb-api
com.sun.xml.bind:jaxb-impl
org.apache.commons:commons-lang3
it.unimi.dsi:fastutil
net.java.dev.jna:jna
net.sf.jopt-simple:jopt-simple
org.apache.logging.log4j:log4j-api
org.apache.logging.log4j:log4j-core
org.eclipse.jetty:jetty-server
io.github.classgraph:classgraph
com.healthmarketscience.rmiio:rmiio

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message