[
https://issues.apache.org/jira/browse/MJAVADOC-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705939#comment-16705939
]
Vincent Massol commented on MJAVADOC-329:
-----------------------------------------
[~rfscholte] As you wish, I don't really need it on my side. Since we're using
the workaround I mentioned in a comment above, producing empty javadoc jars. I
agree that it would be nicer to have package info but we've been doing this for
over 7 years and nobody complained to far. We now have thousands of packages
and it would be quite a large task to document them all at package level. We
have developer doc but on the wiki of the project.
Thanks for asking.
> 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
> Assignee: Robert Scholte
> Priority: Major
>
> 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
(v7.6.3#76005)