[OMID-188] Fix "inconsistent module metadata found" when using hbase-2 - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 1.0.2
Fix Version/s: 1.1.0
Labels:
None

Release Note:

Hide
The maven artifact structure has changed.

Every artifact is built is built separately for HBase 1 and 2. You will need to add the -hbase-1.x or -hbase-2.x suffix to every Omid artifact that you depend on.

You no longer need to specify exclusions when using the HBase 2.x artifacts.

Show
The maven artifact structure has changed. Every artifact is built is built separately for HBase 1 and 2. You will need to add the -hbase-1.x or -hbase-2.x suffix to every Omid artifact that you depend on. You no longer need to specify exclusions when using the HBase 2.x artifacts.

Description

the full message is shown below:

What went wrong:
Execution failed for task ':ohara-common:compileJava'.
> Could not resolve all files for configuration ':ohara-common:compileClasspath'.
   > Could not resolve org.apache.omid:omid-hbase-client-hbase2.x:1.0.1.
   Required by:
   project :ohara-common
> Could not resolve org.apache.omid:omid-hbase-client-hbase2.x:1.0.1.
   > inconsistent module metadata found. Descriptor: org.apache.omid:omid-hbase-client-hbase1.x:1.0.1 Errors: bad module name: expected='omid-hbase-client-hbase2.x' found='omid-hbase-client-hbase1.x'

The root cause is the parent pom still uses profile "hbase-1" so the sub pom has postfix " hbase-1".

In order to resolve this issue, it seems to me the artifactId of parent should have postfix and the pom of parent should be rewrite according to profile (when building release). That makes sub pom can find correct parent pom.