[
http://jira.jboss.com/jira/browse/JBESB-1772?page=comments#action_12414521 ]
Daniel Bevenius commented on JBESB-1772:
----------------------------------------
I added the javadoc generation to the build.xml in product. This may seem the wrong place
for this and I agree.
This should probably be a target in services/base-build.xml, which is imported by all the
services (except soapui-client).
Then we could simply have a 'javadoc' target in services/build.xml that uses
'subant' to call all the javadoc targets in all services.
This would let us add services without having to manually include them in the targets in
services/build.xml. Perhaps all of the targets in services/build.xml should use subant,
that way when new services are added they will be picked up to the main build
automatically.
It makes more sence to them all at once instead of just doing the javadoc stuff now.
Services are not included in javadoc generation
-----------------------------------------------
Key: JBESB-1772
URL:
http://jira.jboss.com/jira/browse/JBESB-1772
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Documentation
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.4
Add a;; the services to the javadocs path in build.xml:
<!-- javadocs paths -->
<path id="org.jboss.esb.javadocs.path">
<pathelement path="build/schema-model/src"/>
<pathelement path="rosetta/src"/>
<pathelement path="services/soapui-client/src/main/java/"/>
</path>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira