[
https://issues.jboss.org/browse/WFLY-233?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on WFLY-233:
-----------------------------------
I could remove most of javadoc related data since it's replaced by a script in the
process anyway. Would that work? IMO it's less risky than creating a separated module,
and would solve the problem of having a large pom.
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.Beta1
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