Allow arbitrary Ant resources as signatures #78
Merged
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
uschindler
added a commit
that referenced
this pull request
Sep 25, 2015
Allow arbitrary Ant resources as signatures
uschindler
added a commit
that referenced
this pull request
Sep 25, 2015
|
I renamed the inner element to simply be |
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.
This allows to add arbitrary resources as signatures to the Ant task. Just put any signature resources inside the element:
<signatures></signatures>This now allows to place anything inside that can be converted to an InputStream (URLs,...). The other inner elements are still supported, but may be deprecated in the future.