Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Over in HBASE-7904, I produced a patch which uses hadoop-2.0 as the default profile.
However, when QA tries to validate compilation against hadoop-2.0:
[ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.apache.hbase:hbase:0.97-SNAPSHOT (/Users/tyu/trunk/pom.xml) has 2 errors [ERROR] 'dependencyManagement.dependencies.dependency.artifactId' for org.apache.hbase:${compat.module}:jar with value '${compat.module}' does not match a valid id pattern. @ line 979, column 21 [ERROR] 'dependencyManagement.dependencies.dependency.artifactId' for org.apache.hbase:${compat.module}:test-jar with value '${compat.module}' does not match a valid id pattern. @ line 984, column 21
We should enhance test-patch.sh so that patch with hadoop-2.0 as default profile doesn't go through validation step against hadoop-2.0
Ideally, the changes in various pom.xml files should be saved as template. User can specify the hadoop profile to test against in the header of patch file.
e.g.
This patch uses hadoop-2.0 as default profile
Index: hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java