[jboss-jira] [JBoss JIRA] (WFLY-233) Move javadoc configuration into a separate module pom
[
https://issues.jboss.org/browse/WFLY-233?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on WFLY-233:
-----------------------------------
The config is generated from the data contained in modules.xml and few .txt files in
$EAP/build/javadoc/ src dir. It was always like that, I just thought I would create some
build hook to update that automatically for AS, but that wouldn't be stable enough.
Plus, AS javadoc isn't really created often.
Move javadoc configuration into a separate module pom
-----------------------------------------------------
Key: WFLY-233
URL: https://issues.jboss.org/browse/WFLY-233
Project: WildFly
Issue Type: Enhancement
Components: Build System
Reporter: Paul Gier
Assignee: Ondrej Zizka
Fix For: 8.0.0.Alpha4
There is a lot of javadoc configuration information in build/pom.xml. Since this pom is
already pretty large even without the javadoc config, it might be good to move the javadoc
generation to a separate module and pom.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira