You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/01/17 04:42:13 UTC

[GitHub] [maven-javadoc-plugin] cowwoc edited a comment on pull request #104: [MJAVADOC-694] Avoid empty warn message from getResolvePathResult

cowwoc edited a comment on pull request #104:
URL: https://github.com/apache/maven-javadoc-plugin/pull/104#issuecomment-1014134830


   @rfscholte Are you sure that `<jdkToolchain>` works properly? @slawekjaranowski mentioned there are no tests for it and when I run the following with JDK 8:
   
   ```
   <plugin>
   	<groupId>org.apache.maven.plugins</groupId>
   	<artifactId>maven-javadoc-plugin</artifactId>
           <version>3.3.1</version>
   	<executions>
   		<execution>
   			<id>attach-javadocs</id>
   			<goals>
   				<goal>jar</goal>
   			</goals>
   			<configuration>
   				<jdkToolchain>
   					<version>11</version>
   				</jdkToolchain>
   				<!-- ... --->
   		</execution>
   	</executions>
   </plugin>
   ```
   
   I get:
   
   ```
   [INFO] Toolchain in maven-javadoc-plugin: JDK[C:\Program Files\Java\jdk-11.0.2]
   org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.3.1:jar (attach-javadocs) on project core: Execution attach-javadocs of goal org.apache.maven.plugins:maven-javadoc-plugin:3.3.1:jar failed.
   [...]
   Caused by: java.lang.UnsupportedOperationException
       at org.codehaus.plexus.languages.java.jpms.CmdModuleNameExtractor.getModuleName (CmdModuleNameExtractor.java:46)
   ```
   
   I tried running against `3.3.2-SNAPSHOT` from Maven Central and got the same result.
   
   The exception seems to imply that JDK 8 is being used in spite of the JDK 11 toolchain resolving properly. Should I open a separate bug report for this?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org