Explicitly declare inputs to the Test task #997
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…anging `<lastUpdated>20230715095719</lastUpdated>`.
e.g. The task was not up-to-date because of the following reasons: Input property '$2' file ... has been added. -> Input property 'localMaven' file ... has been added.
…n it hasn't changed.
… is not re-executed now and doesn't generate more SNAPSHOTs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
to make sure they're re-executed whenever the
:paparazzicode changes.I kept "rerunning tests" after changing Environment.kt, but my changes were not reflected in the test results. I was baffled, until I realized how the paparazzi.jar gets into the test projects.