You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gili (JIRA)" <ji...@apache.org> on 2019/01/22 18:00:00 UTC
[jira] [Comment Edited] (MJAVADOC-567) "Not in a module on the
module source path" when using JDK 12
[ https://issues.apache.org/jira/browse/MJAVADOC-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748952#comment-16748952 ]
Gili edited comment on MJAVADOC-567 at 1/22/19 5:59 PM:
--------------------------------------------------------
Sounds good :) I'll wait on your update to re-test the "unpackaged Automatic-Module-Name" use-case since that seems to be the hardest case.
was (Author: cowwoc):
Sounds good :) I'll wait on your update to re-test an un"package"d Automatic-Module-Name build using javadoc:aggregate (since that seems to be the hardest case).
> "Not in a module on the module source path" when using JDK 12
> -------------------------------------------------------------
>
> Key: MJAVADOC-567
> URL: https://issues.apache.org/jira/browse/MJAVADOC-567
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.1.0
> Environment: maven-javadoc-plugin 3.1.0-SNAPSHOT
> JDK 12-ea+28
> Reporter: Gili
> Priority: Major
> Attachments: testcase.zip
>
>
> If you take the original testcase from MJAVADOC-555 and run it under JDK 12 you will get a new error message: "error: not in a module on the module source path"
> I trust that MJAVADOC-555 fixed a bug under JDK 11 because the MJAVADOC-555_aggr_mixed integration test was failing before and is now passing, but it looks like we need a separate integration test for JDK 12.
> I am attaching an updated testcase for the problem I am seeing under JDK 12.
> Repro steps:
> # Open the attached testcase
> # Run {{mvn clean javadoc:aggregate}}
> # Build will fail with: {{error: not in a module on the module source path}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)