Remove the OCI parts of the java-maven example - #704
Draft
ted-xie wants to merge 1 commit into
Draft
Conversation
OCI is out of scope for an example that centers on Maven deps for Java builds. The OCI part should be moved to rules_oci. See bazel-contrib/rules_oci#905 Fixes a Bazel Downstream pipeline breakage.
ted-xie
requested review from
Wyverald,
fweikert and
gregestren
as code owners
August 26, 2026 21:16
Contributor
Author
|
Still discussing this with Alex Eagle and co, so will convert to draft. |
ted-xie
marked this pull request as draft
August 26, 2026 21:30
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
1 participant
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.
OCI is out of scope for an example that centers on Maven deps for Java builds. The OCI part should be moved to rules_oci.
See bazel-contrib/rules_oci#905
Fixes a Bazel Downstream pipeline breakage.