[
https://issues.apache.org/jira/browse/FLINK-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550052#comment-14550052
]
ASF GitHub Bot commented on FLINK-2003:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/690#issuecomment-103400415
Yeah, I think that this may impact the compatibility of our code with other
code.
A better approach would be IMHO to try and reduce the length of the
classnames by reducing the nesting of functions and lambdas in scala a bit.
Pull a few methods out rather than using n-level nested lambdas.
> Building on some encrypted filesystems leads to "File name too long" error
> --------------------------------------------------------------------------
>
> Key: FLINK-2003
> URL: https://issues.apache.org/jira/browse/FLINK-2003
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Reporter: Theodore Vasiloudis
> Priority: Minor
> Labels: build, starter
>
> The classnames generated from the build system can be too long.
> Creating too long filenames in some encrypted filesystems is not possible,
> including encfs which is what Ubuntu uses.
> This the same as this [Spark
> issue|https://issues.apache.org/jira/browse/SPARK-4820]
> The workaround (taken from the linked issue) is to add in Maven under the
> compile options:
> {code}
> + <arg>-Xmax-classfile-name</arg>
> + <arg>128</arg>
> {code}
> And in SBT add:
> {code}
> + scalacOptions in Compile ++= Seq("-Xmax-classfile-name", "128"),
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
