Skip to content
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

workingDir in quarkusDev not respected by gradle anymore #26586

Closed
joggeli34 opened this issue Jul 6, 2022 · 5 comments · Fixed by #26729
Closed

workingDir in quarkusDev not respected by gradle anymore #26586

joggeli34 opened this issue Jul 6, 2022 · 5 comments · Fixed by #26729
Labels
area/gradle Gradle kind/bug Something isn't working
Milestone

Comments

@joggeli34
Copy link
Contributor

Describe the bug

We set the workingDir in gradle like the following:

        quarkusDev {
            workingDir = rootProject.projectDir
        }

We use this, so that the configuration config/application.properies is found and loaded for dev-mode. Since 1.10.x this isn't working anymore and it tries to load the config \build\classes\java\main\config\application.properties like when the workingDir is not set.

Expected behavior

It should load the configuration from the workingDir/config/application.properties

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

17

GraalVM version (if different from Java)

No response

Quarkus version or git rev

1.10.1

Build tool (ie. output of mvnw --version or gradlew --version)

gradle 7.4.2

Additional information

No response

@joggeli34 joggeli34 added the kind/bug Something isn't working label Jul 6, 2022
@quarkus-bot quarkus-bot bot added the area/gradle Gradle label Jul 6, 2022
@quarkus-bot
Copy link

quarkus-bot bot commented Jul 6, 2022

/cc @glefloch, @quarkusio/devtools

@glefloch
Copy link
Member

glefloch commented Jul 9, 2022

@joggeli34 do you mean version 1.10.x or 2.10.x ?

@joggeli34
Copy link
Contributor Author

joggeli34 commented Jul 10, 2022 via email

@joggeli34
Copy link
Contributor Author

joggeli34 commented Jul 20, 2022

Any chance this get backported to 2.11.x? As this is blocking us from upgrading to 2.10 and also 2.11

@gsmet
Copy link
Member

gsmet commented Jul 20, 2022

@joggeli34 too late for 2.11.0.Final unfortunately but I marked it for backport for 2.11.1.Final that will be released in ~2 weeks.

@gsmet gsmet modified the milestones: 2.12 - main, 2.11.1.Final Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gradle Gradle kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants