[
https://issues.apache.org/jira/browse/FLINK-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177717#comment-15177717
]
ASF GitHub Bot commented on FLINK-3569:
---------------------------------------
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/1757
[FLINK-3569] set Maven Surefire working directory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink FLINK-3569
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1757.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1757
----
commit 3239339480323645839921b9cdc8e5699614d7fc
Author: Maximilian Michels <[email protected]>
Date: 2016-03-03T11:51:26Z
[FLINK-3569] set Maven Surefire working directory
commit f90dcf134f8180b377a8530452bbc05058504d7a
Author: Maximilian Michels <[email protected]>
Date: 2016-03-03T11:52:32Z
[maven] explicitly disable shading of flink-dist
- shading was previously disabled through setting the force-shading
dependency to provided
----
> Test cases fail due to Maven Shade plugin
> -----------------------------------------
>
> Key: FLINK-3569
> URL: https://issues.apache.org/jira/browse/FLINK-3569
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Affects Versions: 1.0.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Fix For: 1.0.0, 1.1.0
>
>
> Tests like the {{ClassLoaderITCase}} use relative paths to find some jars.
> The working directory (basedir) is changed by the Maven Shade plugin when it
> has {{dependencyReducedPomLocation}} configured.
> Thus, we need to explicitly set the working directory (if possibly in the
> plugin configuration) or prevent shading from execute.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
