Re: [D] Badly formatted status msg in AbstractDriverManagerConnectionSource [logging-log4j2]

GitHub user ppkarwasz added a comment to the discussion: Badly formatted status msg in AbstractDriverManagerConnectionSource Hi @RichMacDonald — great catch! 💯 This issue has actually been present since version `2.22.0` (commit 4c53356bc08a81d374eca42adcfea67aa5384f1e), so thank you for spott

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

GitHub user ppkarwasz added a comment to the discussion: java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options > Due to our steps to keep deprecated code out of the codebase, this

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

GitHub user ppkarwasz added a comment to the discussion: java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options Hi @jbisotti, Thanks for the feedback regarding version `2.25.1` — m

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

GitHub user jbisotti added a comment to the discussion: java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options Adding the two options it's complaining about results in a different f

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

GitHub user jbisotti edited a comment on the discussion: java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options To keep deprecated code out of our codebase, we enable deprecation wa

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

GitHub user jbisotti edited a comment on the discussion: java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options To keep deprecated code out of our codebase, we enable deprecation wa

Re: [D] java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options [logging-log4j2]

GitHub user jbisotti added a comment to the discussion: java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options To keep deprecated code out of our codebase, we enable deprecation war