https://bz.apache.org/bugzilla/show_bug.cgi?id=66631
--- Comment #2 from Michael Osipov <micha...@apache.org> --- (In reply to Mark Thomas from comment #1) > Yes, this applies to most of the Tomcat 9 JARs. > > Tomcat uses BND to insert the module-info.class file. > > A review of the BND documentation and source code indicates the location of > the file is hard coded (so is the class version but that has to be >= Java 9 > to specify the module). > > Including a module-info.class file in a JAR otherwise compiled for Java 8 is > a fairly common approach to initial JPMS support. I wonder if updating the > logic in the Maven Project Info Reports Plugin to account for this wouldn't > be a better approach. > > Another option would be requesting BND to add an option to insert > module-info.class under META-INF/versions/9 but I'm not sure "so the Maven > Project Info Reports Plugin gets the right answer" would be a sufficient > justification to get that implemented. Thanks, Mark. MPIR with Maven Shared JAR was just an example of class file analyzers. There are likely others which might trip over this and report the entire JAR as Java 9 which it isn't obviously. I'd like to get this solved rather in BND than Maven Shared JAR which is just the affected downstream analyzer library. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
