quarkus: Eclipse Maven Update "Too Many Files" with 2.7.1
Describe the bug
Upgraded an existing 2.5.1 project to 2.7.1 and then in Eclipse, ran Maven Update. The Maven Update failed with IO errors for “Too Many Files”.
On 2.5.1 lsof -p <PID> | wc -l on the Eclipse process shows just over 1,000 open files for my project.
On 2.7.1 it blows through the 10,420 limit and fails. Examining the raw list of files from lsof -p <PID> shows many duplicate references to the same files which does not occur for 2.5.1. Looks like it’s loading each dependent jar once for each and every project/module.
Expected behavior
Maven Update should succeed.
Actual behavior
Maven Update fails.
How to Reproduce?
Create a multi-module Maven project.
Import into Eclipse.
Perform “Maven Update” in Eclipse.
Use lsof -p <PID> to observe loaded files.
You may not hit the “Too Many Files” error unless you add enough modules, but you’ll still see the increased file count and duplicates versus the 2.5.1 behaviour.
P.S. Can be useful to open Eclipse with the -clean option between tests to ensure there aren’t cached files included (mine was showing some 2.7.1 files even after switching back to 2.5.1).
Output of uname -a or ver
Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_ARM64_T6000 arm64
Output of java -version
Java™ SE Runtime Environment (build 17.0.2+8-LTS-86)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.7.1
Build tool (ie. output of mvnw --version or gradlew --version)
Maven 3.8.4
Additional information
Also tested on non Apple Silicon, same result.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 25 (15 by maintainers)
Yes I could.