[
https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin....
]
Mark Little commented on JBTM-2286:
-----------------------------------
Two questions:
1) is this being driven by any customer/community request?
2) presumably the javadocs generated will always depend upon the build you perform, e.g.,
JTS doesn't get covered if I'm only building core?
Merge javadocs
--------------
Key: JBTM-2286
URL:
https://issues.jboss.org/browse/JBTM-2286
Project: JBoss Transaction Manager
Issue Type: Task
Components: Documentation
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Fix For: 5.0.4
Currently javadocs are split by component. It would be more convenient to have one bundle
of javadocs of all project.
What we are proposing is to produce a single Javadoc artifact for the Narayana project
which has all the public API stuff (ignoring **/internal/**). Same as what you get with
the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)