Re: jspecify dependency

--0000000000006f89a4062195f6b1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I happened to stumble upon this also today and reported it at:
https://issues.apache.org/jira/browse/LOG4J2-3688
To work-around this log4j bug, it should be sufficient to add jspecify to
your `compileOnly` dependencies.

Cheers
Bj=C3=B6rn

Am So., 8. Sept. 2024 um 08:01 Uhr schrieb Ralph Goers <
[email protected]>:

> There was a discussion about this on the dev list back in January.
> Supposedly the library isn=E2=80=99t required at runtime. But if it is in=
cluded in
> module-info I am not sure how you get around that.
>
> Ralph
>
> > On Sep 7, 2024, at 5:39=E2=80=AFPM, PJ Fanning <[email protected]> w=
rote:
> >
> > Hi,
> > I just upgraded and then quickly reverted Apache POI to use the 2.24.0
> release.
> > I'm getting CI build issues where I see this:
> >
> > error: module not found: org.jspecify
> >
> > I can't see anything in the release notes about jspecify.
> >
> > Is there any guidance on what log4j 2.24.0 users need to do regarding
> org.jspecify dependency. I've never had to add this dependency before -
> this is the first time I've ever come across the jspecify project.
> >
> > Any guidance would be appreciated.
> >
> > Regards,
> > PJ
> >
> > ---------------------------------------------------------------------
> > 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]
>
>

--0000000000006f89a4062195f6b1--