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

Michael Osipov edited comment on MJAVADOC-742 at 2/20/23 9:01 AM:
------------------------------------------------------------------

Also now tried with latest maven

{noformat}
..\apache-maven-3.9.0\bin\mvn --version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: E:\projects\workspaces\playground\MJAVADOC-742\apache-maven-3.9.0
Java version: 17.0.5, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.5.8-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" 
{noformat}
and still same result. But if I use java 11, then I get your result. So it 
looks like a different behavior with Java 17.


was (Author: tario):
Also now tried with latest maven

 
{code:java}
..\apache-maven-3.9.0\bin\mvn --version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: E:\projects\workspaces\playground\MJAVADOC-742\apache-maven-3.9.0
Java version: 17.0.5, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.5.8-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" {code}
and still same result. But if I use java 11, then I get your result. So it 
looks like a different behavior with Java 17.

 

 

 

> [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
>
> 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