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 11:03:00 GMT

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

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

stoty commented on pull request #1026:
URL: https://github.com/apache/phoenix/pull/1026#issuecomment-748458232


   :broken_heart: **-1 overall**
   
   
   
   
   
   
   | Vote | Subsystem | Runtime | Comment |
   |:----:|----------:|--------:|:--------|
   | +0 :ok: |  reexec  |   0m 36s |  Docker mode activated.  |
   ||| _ Prechecks _ |
   | +1 :green_heart: |  dupname  |   0m  0s |  No case conflicting files found.  |
   | +1 :green_heart: |  @author  |   0m  0s |  The patch does not contain any @author tags.
 |
   | -1 :x: |  test4tests  |   0m  0s |  The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please list what manual
steps were performed to verify this patch.  |
   ||| _ master Compile Tests _ |
   | +0 :ok: |  mvndep  |   5m 23s |  Maven dependency ordering for branch  |
   | +1 :green_heart: |  mvninstall  |  10m 13s |  master passed  |
   | +1 :green_heart: |  compile  |   1m 17s |  master passed  |
   | +1 :green_heart: |  javadoc  |   1m 51s |  master passed  |
   ||| _ Patch Compile Tests _ |
   | +0 :ok: |  mvndep  |   0m 17s |  Maven dependency ordering for patch  |
   | -1 :x: |  mvninstall  |   0m 20s |  root in the patch failed.  |
   | -1 :x: |  compile  |   0m 19s |  root in the patch failed.  |
   | -1 :x: |  javac  |   0m 19s |  root in the patch failed.  |
   | +1 :green_heart: |  whitespace  |   0m  0s |  The patch has no whitespace issues.  |
   | +1 :green_heart: |  xml  |   0m  3s |  The patch has no ill-formed XML file.  |
   | -1 :x: |  javadoc  |   0m 19s |  root in the patch failed.  |
   | -1 :x: |  javadoc  |   0m  8s |  phoenix-core in the patch failed.  |
   ||| _ Other Tests _ |
   | -1 :x: |  unit  |   0m 24s |  root in the patch failed.  |
   | -1 :x: |  asflicense  |   0m 18s |  The patch generated 1 ASF License warnings.  |
   |  |   |  22m 11s |   |
   
   
   | Subsystem | Report/Notes |
   |----------:|:-------------|
   | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/artifact/yetus-general-check/output/Dockerfile
|
   | GITHUB PR | https://github.com/apache/phoenix/pull/1026 |
   | Optional Tests | dupname asflicense javac javadoc unit xml compile |
   | uname | Linux f5346a240e3d 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux |
   | Build tool | maven |
   | Personality | dev/phoenix-personality.sh |
   | git revision | master / 3d9627f |
   | Default Java | Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08 |
   | mvninstall | https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/artifact/yetus-general-check/output/patch-mvninstall-root.txt
|
   | compile | https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/artifact/yetus-general-check/output/patch-compile-root.txt
|
   | javac | https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/artifact/yetus-general-check/output/patch-compile-root.txt
|
   | javadoc | https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/artifact/yetus-general-check/output/patch-javadoc-root.txt
|
   | javadoc | https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/artifact/yetus-general-check/output/patch-javadoc-phoenix-core.txt
|
   | unit | https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/artifact/yetus-general-check/output/patch-unit-root.txt
|
   |  Test Results | https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/testReport/
|
   | asflicense | https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/artifact/yetus-general-check/output/patch-asflicense-problems.txt
|
   | Max. process+thread count | 88 (vs. ulimit of 30000) |
   | modules | C: . phoenix-core U: . |
   | Console output | https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1026/1/console
|
   | versions | git=2.7.4 maven=3.3.9 |
   | Powered by | Apache Yetus 0.12.0 https://yetus.apache.org |
   
   
   This message was automatically generated.
   
   


----------------------------------------------------------------
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