Fix "Class-Path" parsing issues in -dev.jar generated by Gradle #5988
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
…t run into issues related to "Class-Path" attribute parsing in the Manifest file of the jar
gastaldi
approved these changes
Dec 6, 2019
gsmet
added
the
triage/waiting-for-ci
dmlloyd
approved these changes
Dec 6, 2019
|
Test failure is unrelated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
#4527 and #5808 fixed issues related to the
Class-Pathattribute in the manifest file of the-dev.jarthat we generate. However, those fixes addressed the issue only in the Maven plugin/Mojo and missed out their Gradle counterpart. This PR brings in those same fixes into the Gradle plugin.