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

**[Stefano Chizzolini](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER299015)** opened **[MJAVADOC-745](https://issues.apache.org/jira/browse/MJAVADOC-745?redirect=false)** and commented

The current implementation of taglet auto-detection (initial feature request: MJAVADOC-204) lacks proper evaluation of the dependency tree of configured taglet artifacts (see [](https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#tagletArtifacts)): _each artifact on the taglet classpath is scanned separately_ (see [AbstractJavadocMojo.addTagletsFromTagletArtifacts(..)](https://github.com/apache/maven-javadoc-plugin/blob/a5db96e7e16cc432d8fdea05f460f6c3fa258ba9/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L5901) and [JavadocUtil.getTagletClassNames(..)](https://github.com/apache/maven-javadoc-plugin/blob/a5db96e7e16cc432d8fdea05f460f6c3fa258ba9/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java#L721)), _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).

---

**Affects:** 3.4.1

Start by reading AbstractJavadocMojo.addTagletsFromTagletArtifacts(..) and JavadocUtil.getTagletClassNames(..), which currently scan each configured taglet artifact separately. Trace how the taglet class loader sees dependencies, then verify that auto-detection handles a taglet hierarchy spread across multiple artifacts instead of failing during class loading.

Written by the indexing model from the issue text.