Uwe Schindler

The problem is if JDBI is a module in your app. JDBI as caller can't make a class in your module accessible.

> > 19 / 26 files viewed > > I wonder if we could/should also put the assert versions in question on the 'forbidden list' e.g. https://github.com/apache/solr/tree/main/gradle/validation/forbidden-apis or in some...

We can delay this to a separate PR. I also need try and error for this, because @dweiss implemented that Gradle code which picks the signatures files from that folder.

Thanks for the suggestion! I will look into that - including an Eclipse integration as requested by @rmuir

Hi, we are using globs to allow exclusion of classes. I agree it would be fine to allow this for methods and fields, too! But this is hard to implement...

My suggestion about POI would be: In Lucene we also auto-generate source code using jflex, javacc, or antlr. This process also creates broken methods using input streams (or public classes...

> I'll give it a try, to remove the generated methods ... although this might break user code, which works on the xmlbeans directly, How about "fixing" the methods to...

We did this for Java 8's java.time API. I think signatures should look similar. But as with ICU4J, it is hard to maintain the signatures for those ever-changing libraries. It...

Java 8's time API is similar, but the types are much better and a `LocalDateTime` is different from a `ZonedDateTime` and you cannot accidentally convert between them. The only pain...

Hi, `failOnViolation` can be set to false already (since 2.0) for Ant, Maven, and Gradle: http://jenkins.thetaphi.de/job/Forbidden-APIs/javadoc/check-mojo.html#failOnViolation The idea of creating a machine-readable report is good. Unfortunately the JUnit Report format...