Modularize SciJava Ops FLIM #207

Activity

1. gselzer

   added

   enhancement

   on Apr 2, 2024
2. gselzer

   added this to the unscheduled milestone on Apr 2, 2024
3. ctrueden commented on May 22, 2024

   

   ctrueden

   on May 22, 2024

   Last edited by ctrueden

   Member

   More actions

   Unfortunately, scijava-ops-flim not being modularized results in javadoc build errors:

   [ERROR] javadoc: error - The code being documented uses packages in the unnamed module, but the packages defined in https://github.com/scijava/scijava-concurrent/apidocs/ are in named modules.
   [ERROR] javadoc: error - The code being documented uses packages in the unnamed module, but the packages defined in https://github.com/scijava/scijava-ops-spi/apidocs/ are in named modules.
   [ERROR] javadoc: error - The code being documented uses packages in the unnamed module, but the packages defined in https://github.com/scijava/scijava/apidocs/ are in named modules.
   [ERROR] javadoc: error - The code being documented uses packages in the unnamed module, but the packages defined in https://github.com/scijava/scijava-types/apidocs/ are in named modules.
   

   This suggests to me that anyone attempting to link to javadoc of SciJava Ops components, without using JPMS themselves, will run into this problem as well. I am looking into what can be done to mitigate it.

   Edit: setting <doclint>none</doclint> in the scijava-ops-flim POM does not squelch the errors.

   Edit: it is a bug in javadoc which is marked fixed as of Java 18. The fix seems to have been backported, because when running mvn clean test javadoc:javadoc with Zulu OpenJDK 11.0.23+9, it works, whereas I received the above errors when using AdoptOpenJDK 11.0.8+10.

   👍React with 👍1Reacted by Gabriel Selzer