Support deployment and hot deployment of additional web content beyond src/main/resources/META-INF/resources

[aaronanderson]

Description
I am developing a web application on Quarkus like this example that uses React and webpack. I have configured my JavaScript build process to publish resources to the supported src/main/resources/META-INF/resources directory and deployment and hot deployment work. However this location is intended to store version controlled sources and is not an ideal location for generated resources.

In addition to the standard web resource location above I would like for the Quarkus undertow extension to support an additional build directory for both packaging and hot deployment of dynamically generated content. target/generated-resources is my suggestion.

Implementation ideas
Ideally both src/main/resources/META-INF/resources and target/generated-resources could be merged together for both packaging and hot deployment purposes. It appears knownDirectories is already built into the undertow deployment extension so perhaps this enhancement can be accomplished by simply modifying the maven/gradle plugins to support configuring it.

[emmanuelbernard]

Another though I had recently is whether we should support something like this

-Dquarkus.(static|web)resource.path=/some/other/path

Which would add a new path outside the app containing static resources. It could be listened ot for hotdeployment too as needed. That way you can point your backend to the output dir of your front end project and have a zero copy experience.

Feel free to shoot the idea down if it would not be useful in practice

[gsmet]

@emmanuelbernard I think it's probably something we need to figure out for 1.0? WDYT?

[emmanuelbernard]

It’s in the nice to have category for me. Looks like a net new feature we can put post 1.0 if we have too.

…

On Mon 9 Sep 2019 at 12:04, Guillaume Smet ***@***.***> wrote: @emmanuelbernard <https://github.com/emmanuelbernard> I think it's probably something we need to figure out for 1.0? WDYT? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3886?email_source=notifications&email_token=AACJNWB2ZYZVNCY3DICDYPDQIYNTVA5CNFSM4IUAJ2J2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6G7JXI#issuecomment-529396957>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACJNWEFXVQ3R3TG3J3BNN3QIYNTVANCNFSM4IUAJ2JQ> .

[machi1990]

Another though I had recently is whether we should support something like this

-Dquarkus.(static|web)resource.path=/some/other/path

Which would add a new path outside the app containing static resources. It could be listened ot for hotdeployment too as needed. That way you can point your backend to the output dir of your front end project and have a zero copy experience.

Feel free to shoot the idea down if it would not be useful in practice

Hi @emmanuelbernard I am assigning myself this issue as I am planning to give it a go in the coming days.