Add git.properties file with build id#240
Draft
scottkurz wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Scott Kurz <skurz@us.ibm.com>
Member
|
Is this going to play well with the |
Contributor
Author
I think it does, for now...the git.properties file still seems to appear in the final artifact. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I copied this from StackOverflow somewhere. Should the git.properties really go right in the root or META-INF? I'm not even sure why I have the build-helper-maven-plugin and not just the other plugin. Leaving as a draft.