-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Enable quarkus:dev to hot-reload resources from non-standard paths #10298
Comments
Isn't that basically the same as #10234? |
@famod Not sure I fully understand that issue. From what I can tell everything in The advantage of supporting the normal way additional resources are defined with maven directly instead of having quarkus dev specific parameters would be that you do not have to configure things twice with potential divergence issues down the road. |
I would also be interested to see this working from a Gradle-perspective; just unsure what is the right way. |
@hacst Quarkus is only "watching" a defined set of file names. I've created PR #10328 to define custom file names to watch, but those must exist in the respective |
@famod I am unsure but we might be talking about different things here. As I mentioned I'm woefully unaware of quarkus internals an might be using wrong terminology. Using the code-with-quarkus example I can do: $:code-with-quarkus/src/main/resources$ touch foo.bar
$:code-with-quarkus/src/main/resources$ ls ../../../target/classes/
application.properties META-INF org
$:code-with-quarkus/src/main/resources$ curl localhost:8080/hello
hello
$:code-with-quarkus/src/main/resources$ ls ../../../target/classes/
application.properties foo.bar META-INF org As you can see an arbitrarily named file like The specific use case I have right now is additional configuration provided by custom |
I have another use case for this, it would be nice to also exclude the same folders than are exclude on a production build. For example, I don't need to quarkus dev watches for changes on my
|
A potential PR for this #17184 |
Description
quarkus:dev
should allow hot-reloading of resources specified in the pom using build resources entries (see https://maven.apache.org/plugins/maven-resources-plugin/examples/resource-directory.html).Example pom.xml snippet:
The text was updated successfully, but these errors were encountered: