Latest release fails to build Java project
See original GitHub issueI recently upgraded to the latest version (buck-2017.05.04.01
) on macOS.
I get the following error on a project that previously built:
Warning raised by BUCK file parser: ImportError: No module named buck_parser No content to map due to end-of-input at [Source: com.google.common.io.CountingInputStream@36def8d4; line: 1, column: 0]
Any ideas?
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Building Java project shows error: "Build failed, do you want to ...
I am able to reliable reproduce this problem by having both Maven and Gradle build files present in the solution. If I remove...
Read more >Unable to compile java project with maven - Stack Overflow
The problem is your Maven version is too old. It's not compatible with JDK 16. Try to manually install maven version 3.8.1:.
Read more >Building Java & JVM projects - Gradle User Manual
The simplest build script for a Java project applies the Java Library Plugin and optionally sets the project version and selects the Java...
Read more >Failed Builds - Visual Studio App Center - Microsoft Learn
Builds might ignore a key file that was recently moved or renamed. Try selecting Save or Save & Build in the build configuration....
Read more >Apache Maven Tutorial - Vogella.com
Exercise: Create and build a Java project with Maven ... 1, 4.0.0 is the latest version of the pom file structure, usable for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This usually happens when you have an old daemon hanging around from the previous version. We found that
buck kill
orkillall java
(more extreme) to get rid of any old buck daemon processes usually resolves this@njlr You installed v2017.03.29.01, which is the last working one. I can reproduce the issue in this case, it looks like there is an issue during the bottling of the binary.
@kageiit Makes sense, we should do that. For this specific case, I don’t think that the problem is the old buck running.