Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support BOM (bill of materials) poms #129

Open
cgruber opened this issue Apr 29, 2021 · 0 comments
Open

Support BOM (bill of materials) poms #129

cgruber opened this issue Apr 29, 2021 · 0 comments
Labels
Priority-1 Important, and should be fixed for next stable release Type-bug Something isn't working

Comments

@cgruber
Copy link
Collaborator

cgruber commented Apr 29, 2021

BOMs provide pure-metadata references which collect together a package of artifacts. They can be used to provide a single dep which "expands" into a whole set of fixed versioned artifacts. Bazel maven repository should support the use of these.

The basic behavior should be to do one of two things.

  1. Substitute the single bom with its contents
    • This is more what maven had in mind, since the bom sort of doesn't exist
    • Much more complex on kramer, since it adds a second layer of resolution.
  2. Create a no-artifact intermediate dep and treat the bom's deps as that target's deps
    • Adds an indirection - an empty target that is a "pass-through"
    • More bazely - the bom is real, but only metadata
@cgruber cgruber added Priority-1 Important, and should be fixed for next stable release Type-bug Something isn't working labels Apr 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority-1 Important, and should be fixed for next stable release Type-bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant