You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Mingliang Liu (JIRA)" <ji...@apache.org> on 2017/06/06 20:30:18 UTC
[jira] [Created] (HADOOP-14498) HADOOP_OPTIONAL_TOOLS not parsed
correctly
Mingliang Liu created HADOOP-14498:
--------------------------------------
Summary: HADOOP_OPTIONAL_TOOLS not parsed correctly
Key: HADOOP-14498
URL: https://issues.apache.org/jira/browse/HADOOP-14498
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 3.0.0-alpha1
Reporter: Mingliang Liu
# This will make hadoop-azure not show up in the hadoop classpath, though both hadoop-aws and hadoop-azure-datalake are in the classpath.{code:title=hadoop-env.sh}
export HADOOP_OPTIONAL_TOOLS="hadoop-azure,hadoop-aws,hadoop-azure-datalake"
{code}
# And if we put only hadoop-azure and hadoop-aws, both of them are shown in the classpath.
{code:title=hadoop-env.sh}
export HADOOP_OPTIONAL_TOOLS="hadoop-azure,hadoop-aws"
{code}
This makes me guess that, while parsing the {{HADOOP_OPTIONAL_TOOLS}}, we make some assumptions that hadoop tool modules have a single "-" in names, and the _hadoop-azure-datalake_ overrides the _hadoop-azure_. Or any other assumptions about the {{${project.artifactId\}}}?
Ping [~aw].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org