[
https://issues.apache.org/jira/browse/DAFFODIL-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269373#comment-17269373
]
Steve Lawrence commented on DAFFODIL-1474:
------------------------------------------
After running ``sbt compile test`` and counting the lengths of all basenames
and complete paths, the longest basename is 91 characters, and the longest
pathname is 172 characters. This is pretty long, but still leaves ~80
characters for a user to put the daffodil repo where that way, which should be
sufficient in most cases.
I've also tested using the -Xmax-classfile-name option, which just led to
compilation errors, so that isn't a viable solution.
Considering that this still leaves about 80 characters of padding until the 255
limit imposed by some OSs, I'm don't think this is worth changing. If more
people run into this issue, we can reconsider.
Also see DAFFODIL-2406, which we should do at some point, which will probably
get us back a few more characters. Resolving as won't fix.
> Generated class filenames are too long for some systems
> -------------------------------------------------------
>
> Key: DAFFODIL-1474
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1474
> Project: Daffodil
> Issue Type: Improvement
> Components: Infrastructure, Windows
> Reporter: Steve Lawrence
> Priority: Major
> Labels: dev-verify
>
> Some systems, like windows and ecrypted filesystems on linux, have a maximum
> path length of around 255. Due to scalac's autogenerated class names, it's
> very possible to read this limit. We should use the -Xmax-classfile-name
> option to limit the length of these autogenerated names. Note that our
> longest dirnames are about 100 characters, so if we can limit the length of
> filenames to less than 100, that gives users about 50 characters for a root
> directory path, which isn't totally unreasonable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
