I tried a RC1 for RNG and it failed on validation of the BOM within nexus.
The BOM was staged but the GPG signature file did not match the artifact.
I have updated the project to sign and deploy the BOM and will try again
when the change is verified to work for snapshots by the CI builds.
Alex
the
> > commons release process.
> >
> > Alex
> >
> > [1]
> >
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> > [2] https://github.com/jboss/bom-builder-maven-plugin
> > [3]
> >
> https://search.
] https://github.com/gradle-bom/gradle-bom-generator-plugin
> [6]
> https://github.com/junit-team/junit5/blob/main/junit-bom/junit-bom.gradle.kts
> [7] https://repository.apache.org/service/local/staging/deploy/maven2
> [8] https://maven.apache.org/settings.html
> [9]
> https://www.
On Thu, 29 Sept 2022 at 13:21, Xeno Amess wrote:
> even better if we have a BOM for whole apache commons.
>
A BOM specifies what versions are expected to work together. All commons
components are low level and have few dependencies. Ideally a BOM is not
required as we try to ensure binary and fu
er 29, 2022 8:05:14 PM
> To: Commons Developers List
> Subject: Re: [rng] Release 1.5 with Bill Of Materials (BOM)
>
> That sounds like a good idea!
>
> Gary
>
> On Thu, Sep 29, 2022 at 5:27 AM Alex Herbert
> wrote:
>
> > I think RNG is ready for a release.
>
even better if we have a BOM for whole apache commons.
From: Gary Gregory
Sent: Thursday, September 29, 2022 8:05:14 PM
To: Commons Developers List
Subject: Re: [rng] Release 1.5 with Bill Of Materials (BOM)
That sounds like a good idea!
Gary
On Thu, Sep 29
That sounds like a good idea!
Gary
On Thu, Sep 29, 2022 at 5:27 AM Alex Herbert
wrote:
> I think RNG is ready for a release.
>
> In 1.5 the multi-module project rearranges a few methods to default
> interface methods in a different module. This is binary compatible. However
> it requires that a
