Repository navigation
fix(deps): build and release with dependencies from Airlock only - #2639
Merged
Merged
Conversation
lqiu96
approved these changes
Oct 22, 2026
blakeli0
approved these changes
Oct 22, 2026
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.
Summary
Configures
google-api-java-clientso builds and releases against Airlock (maven-3p-trusted) only resolve approved dependencies:clirr-maven-pluginto an opt-inclirr-compatibility-checkprofile (pom.xml,.kokoro/build.sh):clirr-maven-plugin:2.8pulls in 10 legacy POMs and JARs (bcel:5.1,regexp:1.2,dom4j:1.6,jaxen:1.1-beta-4,jdom:b10,xalan:2.5.0,xercesImpl:2.6.2,xom:1.0b3,icu4j:2.6.1,plexus-components:1.1.4) that lack approved licenses inmaven-3p-trusted.clirr:checkexecution into aclirr-compatibility-checkprofile and enables-Pclirr-compatibility-checkwhenJOB_TYPE=clirrin.kokoro/build.sh.plexus-i18nandantlrinfindbugs-maven-pluginandmaven-bundle-plugin(pom.xml):findbugs-maven-plugin:3.0.5andmaven-bundle-plugin:5.1.9pull inplexus-i18n:1.0-beta-7andantlr:2.7.2viadoxia-site-renderer.plexus-i18n:1.0-beta-10(with*:*exclusions for legacy Plexus container artifacts provided by Maven core) andantlr:2.7.7, whichmaven-3p-trustedincludes.org.osgi:org.osgi.core:4.1.0inmaven-bundle-plugin(pom.xml):maven-bundle-plugin:5.1.9directly depends onorg.osgi:org.osgi.core:6.0.0, which evicts the4.1.0transitive dependency declared byorg.apache.felix.bundlerepository:1.6.6andorg.apache.felix.utils:1.6.0.org.osgi:org.osgi.coreon both Felix dependencies so Maven does not probe the evicted4.1.0stub POM (which lacks license metadata in Airlock).xerces:xmlParserAPIs:2.6.2fromcom.google.android:android(google-api-client-android/pom.xml):xerces:xmlParserAPIsfromcom.google.android:android:4.1.1.4(providedscope), since the JDK provides these XML APIs andxmlParserAPIs:2.6.2lacks license metadata in Airlock.