You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Bryan Cutler (JIRA)" <ji...@apache.org> on 2018/06/26 04:41:00 UTC

[jira] [Commented] (ARROW-2743) [Java] Travis CI test scripts did not catch POM file bug fixed in ARROW-2727

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

Bryan Cutler commented on ARROW-2743:
-------------------------------------

My guess is that the local Maven repo had the java-root pom installed.  When the mvn build is running (by default) it will first search the next directory up, followed by the local repo.  If it is in the repo, then it won't cause a problem.  ARROW-2727 changes the default search path for the parent to the correct location, so I'm not sure if there is much to do in Travis except clean the local repo before build.

> [Java] Travis CI test scripts did not catch POM file bug fixed in ARROW-2727
> ----------------------------------------------------------------------------
>
>                 Key: ARROW-2743
>                 URL: https://issues.apache.org/jira/browse/ARROW-2743
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Java - Vectors
>            Reporter: Wes McKinney
>            Priority: Major
>             Fix For: 0.10.0
>
>
> This bug was introduced in ARROW-1780. It is unclear why the bug was not triggered in Travis CI; we should see about fixing that



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)