Cleaning up Maven's POM.xml #4
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
FelicianoTech
pushed a commit
to FelicianoTech/pipelines-java
that referenced
this pull request
Jun 27, 2019
maryjoyanama
added a commit
to maryjoyanama/pipelines-java-1
that referenced
this pull request
Dec 16, 2019
This reverts commit 0c1ae96.
Lapacho99
added a commit
to Lapacho99/pipelines-java
that referenced
this pull request
Oct 24, 2024
update pool data MicrosoftDocs#4
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 PR addresses two issues with the
POM.xmlof Maven;Both these changes strive to make the file much more grokk-able (for users) and easier to write docs for (for AzDev doc maintainers).
I have verified that with these changes Maven is able to publish the test results and code coverage to Pipelines.