You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2020/12/19 11:16:00 UTC
[jira] [Assigned] (OMID-188) Fix "inconsistent module metadata
found" when using hbase-2
[ https://issues.apache.org/jira/browse/OMID-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Istvan Toth reassigned OMID-188:
--------------------------------
Fix Version/s: 1.0.3
Release Note:
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.
Affects Version/s: 1.0.2
Assignee: Chia-Ping Tsai
> Fix "inconsistent module metadata found" when using hbase-2
> -----------------------------------------------------------
>
> Key: OMID-188
> URL: https://issues.apache.org/jira/browse/OMID-188
> Project: Phoenix Omid
> Issue Type: Bug
> Affects Versions: 1.0.2
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Major
> Fix For: 1.0.3
>
>
> the full message is shown below:
> {quote}
> 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'
> {quote}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)