[MJAVADOC-745] Taglet auto-detection fails on complex dependency hierarchy

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.4.1
• Component/s: javadoc
• Assignee: Unassigned
• Reporter: Stefano Chizzolini
• Created: 27/Feb/23 06:52
• Updated: 01/Mar/23 15:09

Description

The current implementation of taglet auto-detection (initial feature request: MJAVADOC-204) lacks proper evaluation of the dependency tree of configured taglet artifacts (see <tagletArtifacts/>): each artifact on the taglet classpath is scanned separately (see AbstractJavadocMojo.addTagletsFromTagletArtifacts(..) and JavadocUtil.getTagletClassNames(..)), causing taglet class loading to fail in case its hierarchy is spread across multiple artifacts (its class loader has visibility only on a single artifact at a time, in the wrong assumption that no intermediate artifact lies between the Taglet interface and its implementations).