Hi all, I was trying to strim down a JDK, all was smooth until I started to work with Tomcat. The issues I hit:
- Tomcat is designed to be fully used with JPMS whereas I would like to be able to use it in the CP if a jlink custom distro (without forking/patching tomcat jar indeed) - module-info use "requires" and no optional dependent modules which lead to way too much dependencies (open the module-info from tomcat-catalina for ex) Indeed there are always workaround and way to achieve what I wanted but I think the JPMS deliveries of Tomat are not friendly so think it is worth thinking about: 1. dropping it 2. making it optional (I assume it can be released in jars with classifiers only) 3. making it more accurate - but this highly depends how the user consumes it (in particular for tomcat embed flavor) Personally I tend to priviledge 1 cause 3 makes it hard to do right but happy with other solutions not requiring to fork. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance>
