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

Haohui Mai commented on HDFS-9340:
----------------------------------

bq. Fantastic. It looks like it's building all the binaries. What was the old 
directory it was trying to compile? libhdfspp/src/main/native in the old 
location?

Yes. Looks like there is a merge error happened during HDFS-9170 / HDFS-9207.

bq. Haohui, is there a flag I can use with maven to run tests on just the 
native code? I'd like to verify all our gmock tests are running before I +1 but 
it's taking a while because I'm running all tests (in a VM) at the moment.

Not yet -- the current pom.xml does not run {{make test}}. Will need to file 
another jira to fix it.

bq. Also Is there a good reference on the build and test systems, ideally 
including the implementation? The set of flags for maven you gave me worked but 
I haven't found much documentation other than the very basic stuff in "How To 
Contribute" and the pages that links to. If there aren't any docs and I have to 
learn from scratch is there anywhere in the tree that you think would be best 
to start looking? Thanks

Can you be more concrete on what kinds of documentation can help here? It will 
be great to capture your experience in the wiki for other contributors.


> libhdfspp fails to compile after HDFS-9207
> ------------------------------------------
>
>                 Key: HDFS-9340
>                 URL: https://issues.apache.org/jira/browse/HDFS-9340
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>         Attachments: HDFS-9340.HDFS-8707.000.patch
>
>
> After the refactor of HDFS-9207 the {{hadoop-hdfs-client}} module fails to 
> compile as it invokes {{cmake}} against a directory that does not exist. It 
> should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to