phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OMID-188) Fix "inconsistent module metadata found" when using hbase-2
Date Sat, 19 Dec 2020 10:40:00 GMT

    [ https://issues.apache.org/jira/browse/OMID-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252157#comment-17252157
] 

ASF GitHub Bot commented on OMID-188:
-------------------------------------

stoty opened a new pull request #1026:
URL: https://github.com/apache/phoenix/pull/1026


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>            Reporter: Chia-Ping Tsai
>            Priority: Major
>
> 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)

Mime
View raw message