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

Provide a bill of materials (BOM) #1264

Closed
bjmi opened this issue Jun 7, 2022 · 1 comment
Closed

Provide a bill of materials (BOM) #1264

bjmi opened this issue Jun 7, 2022 · 1 comment
Assignees
Milestone

Comments

@bjmi
Copy link

bjmi commented Jun 7, 2022

I figured that there is a number of byte-buddy artifacts, so it might be useful to provide a BOM (Bill Of Materials) that lists all versions of all artifacts in a central place.

Such a thing could then be consumed in a Maven multi project build through

<dependencyManagement>
    <dependency>
        <groupId>net.bytebuddy</groupId>
        <artifactId>byte-buddy-bom</artifactId>
        <version>${byte-buddy.version}</version>
        <type>pom</type>
        <scope>import</scope>
    </dependency>
    [...]
</dependencyManagement>

and this could be referenced in individual module files like so:

<dependencies>
    <dependency>
      <groupId>net.bytebuddy</groupId>
      <artifactId>byte-buddy</artifactId>
    </dependency>
    <dependency>
        <groupId>net.bytebuddy</groupId>
        <artifactId>byte-buddy-agent</artifactId>
    </dependency>
    [...]
</dependencies>

Examples:

Creating and publishing such a BOM would help a lot. Thanks!

@raphw
Copy link
Owner

raphw commented Jun 7, 2022

You are right, that's a convenient extra. You will be able to import byte-buddy-parent as a BOM starting with the next release.

@raphw raphw self-assigned this Jun 7, 2022
@raphw raphw added this to the 1.12.11 milestone Jun 7, 2022
@raphw raphw closed this as completed Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants