[ https://issues.apache.org/jira/browse/MJAVADOC-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244381#comment-15244381 ]
Michael Osipov edited comment on MJAVADOC-329 at 4/16/16 8:35 PM: ------------------------------------------------------------------ What about adding a {{packing-info.java}} in the root package which is not internal, the output won't be empty then? was (Author: michael-o): What about adding a {{packing-info.java}} in the root package which is not internal. The output won't be empty then. > Allow generation of empty javadoc JARs > -------------------------------------- > > Key: MJAVADOC-329 > URL: https://issues.apache.org/jira/browse/MJAVADOC-329 > Project: Maven Javadoc Plugin > Issue Type: Improvement > Affects Versions: 2.8 > Reporter: Vincent Massol > > Here's my use case: > * I want to be able to deploy my artifacts to Maven Central. There's a > requirement that a javadoc jar exists for the arifact to deploy > * However I have some maven modules of type packaging = jar that have java > files but these files are located in an "internal" package (internal api that > we don't expose to end users since it's not part of our public API contract) > which we exclude from the javadoc generation > The problem is that the javadoc plugin doesn't generate any JAR if there are > no java files matching (even if I have other files such as a package.html > file in my src/main/javadoc/* directories). > I'd like it to be possible to generate an "empty" javadoc JAR containing only > a package.html file for example. > Thanks a lot -- This message was sent by Atlassian JIRA (v6.3.4#6332)