[#1691] work around maven plugin warnings for maven 3.9.6 #1692
Conversation
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
bmarwell
force-pushed
the
#1691_maven-plugin-warnings
branch
from
867f92a to
0fe8363
Compare
cherylking
reviewed
Jun 13, 2023
| <groupId>io.openliberty.tools</groupId> | ||
| <artifactId>ci.common</artifactId> | ||
| <version>1.8.26</version> | ||
| <exclusions> |
Member
There was a problem hiding this comment.
Do you need to pull in the latest snapshot 1.8.27-SNAPSHOT since you made a change in ci.common?
Contributor
Author
There was a problem hiding this comment.
Not really, this is intended to be a workaround until ci.common was released. After that, the exclusion can be removed again.
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.
Work done similar to what Jacoco did:
jacoco/jacoco#1438
fixes #1691