[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760951#comment-16760951
]
Hudson commented on HDDS-631:
-----------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15892 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15892/])
HDDS-631. Ozone classpath shell command is not working. Contributed by (elek:
rev 194f0b49fb8ae3b876dde82f04f906f0ab0f5bdf)
* (edit) hadoop-ozone/common/src/main/bin/ozone
> Ozone classpath shell command is not working
> --------------------------------------------
>
> Key: HDDS-631
> URL: https://issues.apache.org/jira/browse/HDDS-631
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Nanda kumar
> Assignee: Elek, Marton
> Priority: Blocker
> Fix For: 0.4.0
>
> Attachments: HDDS-631.00.patch, HDDS-631.001.patch
>
>
> In the ozone package (tar) the ozone and its dependency jars are copied to an
> incorrect location. We use to have the jars in {{share/hadoop/<module>}} for
> each module. Those directories are empty now. All the jars are placed in
> {{share/ozone/lib}} directory.
> With this structure when we run {{ozone classpath}} command, we get an
> incorrect output.
> {code}
> $ bin/ozone classpath
> /Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/etc/hadoop:/Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/share/hadoop/common/*
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
