-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"File name too long" error occurs when attempting to assemble a project on an encrypted Linux machine #69
Comments
I don't think there's not much that sbt-assembly could improve to get around this error. Have you seen this thread: https://groups.google.com/forum/?fromgroups=#!topic/simple-build-tool/wtD6vgdiy6g You could try to use the scalac |
I went ahead and mocked up a script to sync-up my dependencies independently, upon deployment... So for my purposes, this can be ignored/closed. But, FYI, to anyone else stumbling across this issue, the above-linked thread indicates that the problem arises when you're building from a home directory that's encrypted. Workarounds include making your |
@jrudolph Thanks for answering this! @JustAHappyKid I am assuming you're also on an encrypted Linux machine, so I renamed the case that way. |
@eed3si9n Yes that's correct -- I'm using an encrypted home directory (or at least recall checking that checkbox upon installation). |
Long path tool can be very helpful on this situation. Thanks |
"Long Path Tool" is a Windows-only program. It's not going to help on an encrypted Ubuntu mount. |
This isn't just encrypted machines. Docker has the limit as well. Anything that tries to use sbt-assemly in a Docker container could fail becuase of this. |
I'm just running into the same problem and the workarounds are not very handy... |
There's a workaround I remember I used to limit the length (although I On Tue, Oct 27, 2015 at 3:57 PM, Martin Mauch notifications@github.com
|
I guess you're referring to using |
Just came across this from some googling and just wanted to post a workaround for anyone having the same issue under docker, but not wanting to recompile third party libs. I mounted a directory from the host server in the docker container using the (more info about mounting directories from the host can be found in the docker docs here) |
Ah, good idea @janstenpickle! I tried incorporating an in-memory FS into sbt-assembly but didn't get very far. |
Can confirm that @janstenpickle suggestion to mount the directory on the host is a perfect workaround, worked like a charm. Thank you ! |
Sorry in advance, as this is as much an OS/file-system limitation as it is a bug in the software, but devising some sort of workaround in this plugin (sbt-assembly) would seem the most practical route.
So, this seems to occur with any project that uses the newly-released Slick library. This is the library-dependency line:
Then, when running
sbt assembly
, you get something like this:The text was updated successfully, but these errors were encountered: