Remove exclusion of META-INF/versions/9/OSGI-INF/MANIFEST.MF. - #6020
Merged
Conversation
[JSpecify 1.0.1](https://github.com/jspecify/jspecify/releases) removed that file from the JSpecify jar. (You can see the history of why the exclusion was added in 2517f1b.) I do notice some other preexisting shading-related diagnostics, though they are only warnings: ``` [INFO] --- shade:3.6.2:shade (default) @ error_prone_refaster --- [WARNING] error_prone_core-1.0-HEAD-SNAPSHOT-with-dependencies.jar, error_prone_refaster-1.0-HEAD-SNAPSHOT.jar define 2 overlapping resources: [WARNING] - META-INF/MANIFEST.MF [WARNING] - META-INF/services/com.sun.source.util.Plugin [WARNING] maven-shade-plugin has detected that some files are [WARNING] present in two or more JARs. When this happens, only one [WARNING] single version of the file is copied to the uber jar. [WARNING] Usually this is not harmful and you can skip these warnings, [WARNING] otherwise try to manually exclude artifacts based on [WARNING] mvn dependency:tree -Ddetail=true and the above output. [WARNING] See https://maven.apache.org/plugins/maven-shade-plugin/ ``` I also notice this: ``` [INFO] --- bnd:7.3.0:bnd-process (generate-OSGi-manifest) @ error_prone_refaster --- [WARNING] Cannot consider developer in line '57' of file '/usr/local/google/home/cpovirk/clients/error-prone-white/error-prone/pom.xml' for bundle header 'Bundle-Developers' as it does not contain the mandatory id. ``` Again, that's unrelated. PiperOrigin-RevId: 962955941
copybara-service
Bot
force-pushed
the
test_962891848
branch
from
August 11, 2026 20:12
236585b to
c46493f
Compare
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
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.
Remove exclusion of
META-INF/versions/9/OSGI-INF/MANIFEST.MF.JSpecify 1.0.1 removed that file from the JSpecify jar.
(You can see the history of why the exclusion was added in 2517f1b.)
I do notice some other preexisting shading-related diagnostics, though they are only warnings:
I also notice this:
Again, that's unrelated.