You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2021/04/30 21:27:00 UTC
[jira] [Closed] (MJAVADOC-676) Can't generate javadoc when project
has an automatic module name
[ https://issues.apache.org/jira/browse/MJAVADOC-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MJAVADOC-676.
-----------------------------------
Resolution: Won't Fix
I really hate the idea that the automatic-module-name entry is only added to claim the name. The whole idea of this entry was to make it possible to start using the module path without using the filename based module name. ( If only the modules had something like a namespace we wouldn't have this discussion). But if modules follow the concept of using the shared package as the module name, then there is no need to claim module names.
I do understand that it is weird that compilation succeeds while javadoc fails, but that is because it is using the jar.
Looking at your pom, there's a better solution: bind the goal to the {{prepare-package}} phase. This way it will be using the target/classes instead of the jar.
I don't want to add a parameter, because the plugin has all the information to detect split packages, but it would also introduce extra code.
I will keep the current behavior, hoping it will motivate library maintainers to only add the module-name their project is indeed java module system ready, but their dependencies aren't yet. Otherwise it will be impossible to start switching to the module path.
In other words: In my opinion neo4j made a very bad decision to add automatic-module-names when their jars are still having split packages. (as if there's a need to claim the module name prefix org.neo4j ... )
> Can't generate javadoc when project has an automatic module name
> ----------------------------------------------------------------
>
> Key: MJAVADOC-676
> URL: https://issues.apache.org/jira/browse/MJAVADOC-676
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Michael Simons
> Assignee: Robert Scholte
> Priority: Major
> Attachments: issues-master.zip
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)