Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Thu, 2 Jun 2016 12:57:59 +0000 (UTC)
From: "Maximilian Michels (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12975143.1464870054000.14933.1464872279156@Atlassian.JIRA>
In-Reply-To: <JIRA.12975143.1464870054000@Atlassian.JIRA>
References: <JIRA.12975143.1464870054000@Atlassian.JIRA> <JIRA.12975143.1464870054538@arcas>
Subject: [jira] [Closed] (FLINK-4009) Scala Shell fails to find library for
 inclusion in test
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Jun 2016 12:58:00 -0000


     [ https://issues.apache.org/jira/browse/FLINK-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maximilian Michels closed FLINK-4009.
-------------------------------------
    Resolution: Duplicate

> Scala Shell fails to find library for inclusion in test
> -------------------------------------------------------
>
>                 Key: FLINK-4009
>                 URL: https://issues.apache.org/jira/browse/FLINK-4009
>             Project: Flink
>          Issue Type: Test
>          Components: Scala Shell, Tests
>    Affects Versions: 1.1.0
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>              Labels: test-stability
>             Fix For: 1.1.0
>
>
> The Scala Shell test fails to find the flink-ml library jar in the target folder. This is due to its working directory being expected in "flink-scala-shell/target" when it is in fact "flink-scala-shell". I'm a bit puzzled why that could have changed recently. The last incident I recall where we had to change paths was when we introduced shading of all artifacts to produce effective poms (via the force-shading module). I'm assuming the change of paths has to do with switching from Failsafe to Surefire in FLINK-3909.


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