When we put a static OpenAPI file in META-INF folder (the default location), the build fails with this error:
C:\projects\acctmgt-back\target\acctmgmt-back.jar -> C:\projects\acctmgt-back\target\acctmgmt-back.jar.original: The process cannot access the file because it is being used by another process.
If we remove the static OpenAPI file then the build is successful.
So apparently Quarkus has a file lock on this file.
We are using 999-SNAPSHOT to pickup some other recent changes.
Note we are building on Windows and generating an uber-jar type.
Expected behavior
Build should not fail
Actual behavior
Build fails
How to Reproduce?
No response
Output of uname -a or ver
No response
Output of java -version
java 21.0.4 2024-07-16 LTS
Quarkus version or git rev
No response
Build tool (ie. output of mvnw --version or gradlew --version)
Describe the bug
When we put a static OpenAPI file in META-INF folder (the default location), the build fails with this error:
C:\projects\acctmgt-back\target\acctmgmt-back.jar -> C:\projects\acctmgt-back\target\acctmgmt-back.jar.original: The process cannot access the file because it is being used by another process.
If we remove the static OpenAPI file then the build is successful.
So apparently Quarkus has a file lock on this file.
We are using 999-SNAPSHOT to pickup some other recent changes.
Note we are building on Windows and generating an uber-jar type.
Expected behavior
Build should not fail
Actual behavior
Build fails
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
java 21.0.4 2024-07-16 LTS
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Additional information
No response