Chainguard Repository for Java#3316
Merged
Merged
Conversation
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: s-stumbo <100295939+s-stumbo@users.noreply.github.com>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <100295939+s-stumbo@users.noreply.github.com>
SharpRake
approved these changes
Jun 11, 2026
SharpRake
left a comment
SharpRake
left a comment
Collaborator
There was a problem hiding this comment.
Changes look great! just some minor suggestions from me
mosabua
reviewed
Jun 11, 2026
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <100295939+s-stumbo@users.noreply.github.com>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
|
|
||
| If you are using direct access with the Chainguard Repository and you want Chainguard policy controls to apply consistently, configure Chainguard as a global Maven mirror. Without a global mirror, Maven can fall back to its built-in Maven Central definition when Chainguard reports a dependency as unavailable, bypassing the expected cooldown behavior for artifacts. | ||
|
|
||
| The following `~/.m2/settings.xml` configures direct access with Chainguard's remediated Java repository as |
Contributor
There was a problem hiding this comment.
Flagging a comment to update this once we verify with vanguard testing what the right settings.xml config should look like.
mosabua
reviewed
Jun 23, 2026
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
mosabua
reviewed
Jun 24, 2026
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
angela-zhang
approved these changes
Jun 25, 2026
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
Member
|
Thanks for taking my feedback into account. This looks great. |
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
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.
[ ] Check if this is a typo or other quick fix and ignore the rest :)
Type of change
Update existing docs for Chainguard Repository support for Java libraries
What should this PR do?
Add content about Java to Chainguard Repository content:
Why are we making this change?
Product update to support Chainguard Repository for Java
What are the acceptance criteria?
Java should be mentioned in content about Chainguard Repository, content should be clear and accurate
How should this PR be tested?
Review the deploy preview to ensure that content appears as expected