[
https://issues.apache.org/jira/browse/HDFS-9416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019277#comment-15019277
]
Allen Wittenauer commented on HDFS-9416:
----------------------------------------
bq. Allen Wittenauer would you please change mvn command line by passing them?
In a nutshell, no.
The Dockerfile used by Jenkins installs these packages in the place where most
Linux systems install those components. There should be zero reason to specify
those locations.
The directives given via Maven are to be used specifically in the case where
the normal locations that are used during autodetection are broken in some way.
For example, the OpenSSL implementation used in OS X Mavericks doesn't support
a feature that libhadoop.so expects to be able to use. Therefore, many people
use homebrew to install it into /usr/local.
> Respect OpenSSL and protobuf definitions in maven configuration when building
> libhdfspp
> ---------------------------------------------------------------------------------------
>
> Key: HDFS-9416
> URL: https://issues.apache.org/jira/browse/HDFS-9416
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: Haohui Mai
> Assignee: Xiaobing Zhou
> Priority: Blocker
> Attachments: HDFS-9416.004.patch, HDFS-9416.HDFS-8707.004.patch,
> HDFS-9416.HDFS-8707.005.patch
>
>
> As discovered in HDFS-9380 the current pom.xml / CMakeLists.txt in libhdfspp
> does not respect the configuration from the maven command line. Subsequently
> it breaks the Jenkins build.
> Both pom.xml and CMakeLists.txt need to be fixed to get Jenkins working again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
