[ https://issues.apache.org/jira/browse/FLINK-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005717#comment-16005717 ]
ASF GitHub Bot commented on FLINK-6414: --------------------------------------- Github user greghogan commented on the issue: https://github.com/apache/flink/pull/3800 @StephanEwen does the recent discussion on packaging shaded dependencies mean that `force-shading` will go away? Or do we keep that even if dependencies are no longer being shaded? Or will only some shaded dependencies (the most problematic) be provided? > Use scala.binary.version in place of change-scala-version.sh > ------------------------------------------------------------ > > Key: FLINK-6414 > URL: https://issues.apache.org/jira/browse/FLINK-6414 > Project: Flink > Issue Type: Improvement > Components: Build System > Affects Versions: 1.3.0 > Reporter: Greg Hogan > Assignee: Greg Hogan > > Recent commits have failed to modify {{change-scala-version.sh}} resulting in > broken builds for {{scala-2.11}}. It looks like we can remove the need for > this script by replacing hard-coded references to the Scala version with > Flink's maven variable {{scala.binary.version}}. > I had initially realized that the change script is [only used for > building|https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/building.html#scala-versions] > and not for switching the IDE environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)