You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The analyzer appears to falsely list a number of dependencies as Unused, such as JSP, JSTL and Thymeleaf. This is presumably because they are not used during compile of java assets. (note that javax/jakarta JSP is defined as 'runtime' but JSTL and Thymeleaf have to be scope=compile)
There are plugins, such as the io.leonard.maven.plugins jspc maven plugin, which can e used to compile JSP's during local build and thus making them available for analysis. It would be a big benefit if depclean could invoke those plugins to compile those jsp and html files (Thymeleaf) so they can be analyzed and thus reduce the number of false positives flagged as unused.
The text was updated successfully, but these errors were encountered:
The analyzer appears to falsely list a number of dependencies as Unused, such as JSP, JSTL and Thymeleaf. This is presumably because they are not used during compile of java assets. (note that javax/jakarta JSP is defined as 'runtime' but JSTL and Thymeleaf have to be scope=compile)
There are plugins, such as the io.leonard.maven.plugins jspc maven plugin, which can e used to compile JSP's during local build and thus making them available for analysis. It would be a big benefit if depclean could invoke those plugins to compile those jsp and html files (Thymeleaf) so they can be analyzed and thus reduce the number of false positives flagged as unused.
The text was updated successfully, but these errors were encountered: