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/04 12:18:00 UTC

[jira] [Commented] (OMID-192) fix missing jcommander dependency

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

Istvan Toth commented on OMID-192:
----------------------------------

This is caused by upgrading maven-assembly-module, where the new version does something differently, based on the scope of the included dependent module.

The real problem is the that Omid mixes code and assemblies in the same subproject, which makes it impossible to define the dependencies properly.

My proposed fix changes the dependency to runtime, which is rather arbitrary, but this one seems to be the scope that impacts the code the least, while fixing the assembly contents.


> fix missing jcommander dependency
> ---------------------------------
>
>                 Key: OMID-192
>                 URL: https://issues.apache.org/jira/browse/OMID-192
>             Project: Phoenix Omid
>          Issue Type: Bug
>            Reporter: Richard Antal
>            Assignee: Istvan Toth
>            Priority: Major
>
> When I started the the **_omid.sh create-hbase-commit-table
> _I got the following exception:
> {{}}
> {code:java}
> Error: A JNI error has occurred, please check your installation and try again
> Exception in thread "main" java.lang.NoClassDefFoundError: com/beust/jcommander/ParameterException{code}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)