-
Notifications
You must be signed in to change notification settings - Fork 935
-
Notifications
You must be signed in to change notification settings - Fork 935
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
Intermittent java.io.FileNotFoundException on release #2301
Comments
It's hard to tell what's going on without repro steps. Maybe you should raise it up on sbt-release if there are others who's seeing the same thing. |
I noticed that changing the file that contained the class seems to force SBT to recompile it and it makes the error go away. It's also somewhat random which file it is. This suggests to me that SBT is doing something in parallel. Build file:
plugins
We have a maven fan join our team recently, they are going to try to rewrite our build with maven, and if they succeed we will just use maven from now on ... it seems everyone just says maven is much more stable. |
Hi, is there any update on this issue? We're experiencing this in our build. Every other deploy attempt ends with this exception. |
FYI we had this problem as well when using sbt-assembly 0.14.0 and it's fixed now with sbt-assembly 0.14.3. Like in the build file above we are using shading and I believe that was causing the problem. It seems that it was fixed by this: sbt/sbt-assembly#197 |
I'm happy to go with that and close this ticket. |
I've updated sbt-assembly to 0.14.3 - and this did not solve my case. I'm still experiencing the same thing with updated version. |
I've used assembly 0.14.1 with shading and exprienced a similar issue - random failure due to FileNotFoundException. I've upgraded to assembly 0.14.5 and the issue completely disappeared. |
It looks like generally the problem is related to sbt-assembly, so I am closing this here. |
When running
we get the following stacktrace, but it works OK with
sbt assembly
. What is really weird is it only happens sometimes, sometimes it works!The text was updated successfully, but these errors were encountered: