You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running Quarkus with mvn quarkus:dev, .env file at project root gets replace with symbolic link pointing to that same location. The behaviour seems to be related to having workingDirset in pom.xml.
Expected behavior
While running Quarkus in dev mode .env should be read from project root.
Actual behavior .env file at project root gets replaced with symbolic link pointing to the same location.
Describe the bug
When running Quarkus with
mvn quarkus:dev
,.env
file at project root gets replace with symbolic link pointing to that same location. The behaviour seems to be related to havingworkingDir
set in pom.xml.Expected behavior
While running Quarkus in dev mode
.env
should be read from project root.Actual behavior
.env
file at project root gets replaced with symbolic link pointing to the same location.To Reproduce
Steps to reproduce the behavior:
.env
file at the rootmvnw quarkus:dev
.env
file is replaced with symbolic link pointing to itConfiguration
Environment (please complete the following information):
uname -a
orver
:java -version
: openjdk version "11.0.6" 2020-01-14mvnw --version
orgradlew --version
):Additional context
I am using Quarkus with the Camel extension and for the use case setting
workingDir
seem to be a requirement.The text was updated successfully, but these errors were encountered: