Github user jeroenvlek commented on a diff in the pull request:
https://github.com/apache/gora/pull/21#discussion_r25929774
--- Diff: gora-hbase/pom.xml ---
@@ -117,6 +117,18 @@
<dependency>
<groupId>org.apache.hbase</groupId>
+ <artifactId>hbase-common</artifactId>
+ <scope>compile</scope>
+ <exclusions>
+ <exclusion>
+ <groupId>org.slf4j</groupId>
+ <artifactId>slf4j-log4j12</artifactId>
--- End diff --
http://basementcoders.com/2010/05/maven-exclusions-not-always-inherited/
It depends. According to the link above, this exclusion actually causes the
other exclusions in the main pom.xml to be *included* again. Is that on
purpose? Do we then still need the other exclusions in the parent pom.xml?
My knowledge of Maven runs a bit short here. The difference with the
example in the link above, is that in the parent pom one exclusion is stated
in a dependency management section, and the child pom just states its
dependencies.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
