[ 
https://issues.apache.org/jira/browse/MJAVADOC-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693247#comment-17693247
 ] 

Peter Verhas commented on MJAVADOC-742:
---------------------------------------

I also got into this issue with my [https://github.com/verhas/jamal] project. 
In this case, I could get to the point that I could see that version 3.4.1 
generates an `options` file with

```

'/Users/verhasp/.m2/repository/com/javax0/jamal/jamal-doclet/1.12.6/jamal-doclet-1.12.6.jar:/Users/verhasp/.m2/repository/com/javax0/jamal/jamal-api/1.12.6/jamal-api-1.12.6.jar:/Users/verhasp/.m2/repository/com/javax0/jamal/jamal-tools/1.12.6/jamal-tools-1.12.6.jar:/Users/verhasp/.m2/repository/com/javax0/levenshtein/1.0.0/levenshtein-1.0.0.jar:/Users/verhasp/.m2/repository/com/javax0/jamal/jamal-engine/1.12.6/jamal-engine-1.12.6.jar:/Users/verhasp/.m2/repository/com/javax0/jamal/jamal-core/1.12.6/jamal-core-1.12.6.jar'

```

 

The same `options` file generated by the plugin 3.5.0 contains

```

'/Users/verhasp/.m2/repository/com/javax0/jamal/jamal-doclet/1.12.6/jamal-doclet-1.12.6.jar'

```

 

The missing JARs are those are the transitive dependencies of the doclet 
artifact.

 

When you fix this issue pay attention to do the same for the `-tagletpath` 
option as well. It suffers from the same issue.

 

A possible workaround (not tried) is to add all the dependencies to the POM 
file.

> [REGRESSION] Transitive dependencies of docletArtifact missing
> --------------------------------------------------------------
>
>                 Key: MJAVADOC-742
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-742
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>          Components: javadoc
>    Affects Versions: 3.5.0
>            Reporter: Patrick Ruckstuhl
>            Priority: Blocker
>             Fix For: 3.5.1
>
>
> It looks like with 3.5.0 transitive dependencies of the docletArtifact are no 
> longer added to the classpath and generation fails with class not found. 
> Reverting back to 3.4.1 everything works fine.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to