Resolve competing war and jetty run definitions #5329
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This work removes the need for a
mvn process-resources
when trying out changes usingjetty:run
, instead files are edited directly.This pull request seeks to make
jetty:run
work directly from many folders and file locations for quick feedback, while lettingwar:war
be very explicit about working with named and versioned dependencies for isolated builds.The gold standard we are working for here is the ability to check out a branch to work on a single problem only building the modules that are being changed. Description from proposal: Resolve competing web module war definitions
Since this proposal was written additional needless complexity has been pointed out, this can be explored in subsequent pull requests.