I am not aware of any tooling to easily check for the module-info
class. If anyone is aware of anything, get in touch.
I am not super enthusiastic about writing something custom. A naive
implementation could check that all jars in a directory contain a
module-info.class but that doesn't validate the contents.
The funny thing is that our Gradle build does test with the
module-info classes. It just doesn't ensure that they end up in the
jars.
I do intend to make a few minor jar upgrades but nothing significant.
commons-io and pdfbox patches became available today, for instance.

On Tue, 18 Nov 2025 at 18:38, Dominik Stadler
<[email protected]> wrote:
>
> Hi,
>
> A quick bugfix release soon sounds good. A very quick check of building
> 5.5.1 locally and comparing with 5.5.0 only showed the expected module-file
> being included now.
>
> We can hopefully skip full regression testing as code-changes are very
> small.
>
> Is there a way how we can automatically check for this in the future?
>
> Thanks... Dominik.
>
>
> On Mon, Nov 17, 2025 at 6:51 PM PJ Fanning <[email protected]> wrote:
>
> > There was an issue where the module-info classes were omitted from the
> > published jars.
> > I have created a 5.5.x branch and a CI build for it. The trunk branch
> > already has 6.0.0 oriented changes in it.
> > I have a fix committed but I would appreciate if the fix is
> > independently verified.
> >
> > I would suggest that we should create a 5.5.1 RC1 but maybe we could
> > wait a few days (or even a week) to see if any other issues arise.
> >
> > https://github.com/apache/poi/issues/932
> >
> > I can act as release manager for 5.5.0 but if anyone else wants to
> > give it a go, get in touch.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to