Mark .form files as inputs to :instrumentForms task #4685
Merged
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.
Identify the Bug or Feature request
Improves on PR #4390 for #4389
Description of the Change
I've noticed that the current
:instrumentForms
task does not recognize changes to IntelliJ GUI files. This makes dev iteration more clunky than it needs to be when making frequent UI changes. So the situation was only mildly improved by the previous PR.This PR makes it so the class files are reinstrumented whenever a
.form
file is changed. This way they won't report as up-to-date unless neither Java nor form files are modified.Possible Drawbacks
Should be none (build only).
Documentation Notes
N/A
Release Notes
N/A
This change is![Reviewable](https://camo.githubusercontent.com/23b05f5fb48215c989e92cc44cf6512512d083132bd3daf689867c8d9d386888/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)