[HBASE-15925] compat-module maven variable not evaluated

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
• Fix Version/s: 1.3.0, 1.2.2, 1.1.6, 2.0.0
• Component/s: build
• Release Note: Downstream users of HBase dependencies that do not properly activate Maven profiles should now see a correct transitive dependency on the default hadoop-compatibility-module.
• Assignee: Sean Busbey
• Reporter: Nick Dimiduk
• Created: 31/May/16 16:13
• Updated: 09/Nov/17 01:04
• Resolved: 08/Jul/16 15:41

Description

Looks like we've regressed on HBASE-8488. Have a look at the dependency artifacts list on http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1. Notice the direct dependency's artifactId is ${compat.module}.

Issue Links

• is related to: HBASE-8488 HBase transitive dependencies not being pulled in when building apps like Flume which depend on HBase