Include LICENSE in the generated jar under META-INF.
#32
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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=80&v=4){kind=small}
copybara-service
bot
force-pushed
the
test_530400894
branch
from
573dbf7 to
9a249f7
Compare
See google/guava#6468 and google/guava#6477. I cowardly did not look into Auto and its many pom.xml files. And I gave up on jimfs when its jar didn't end up containing the license... maybe somehow related to how it has other files autogenerated into `META-INF`?? RELNOTES=n/a PiperOrigin-RevId: 530613491
copybara-service
bot
force-pushed
the
test_530400894
branch
from
9a249f7 to
0631a72
Compare
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.
Include
LICENSEin the generated jar underMETA-INF.See google/guava#6468 and google/guava#6477.
I cowardly did not look into Auto and its many pom.xml files. And I gave up on jimfs when its jar didn't end up containing the license... maybe somehow related to how it has other files autogenerated into
META-INF??RELNOTES=n/a