[
https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028282#comment-13028282
]
Karl Wright edited comment on CONNECTORS-194 at 5/3/11 4:08 PM:
----------------------------------------------------------------
cli-xconf seems definitely the way to go. But we're still going to need a
jumping-off page that is handled by Forrest (which is what javadoc.html does
for us). Moving javadoc.html to api/index.html for this purpose is also OK if
we can get forrest to work with it properly in that location. If the "api"
subdirectory is the new place where the javadoc roots are all put, that's fine
by me.
was (Author: kwri...@metacarta.com):
cli-xconf seems definitely the way to go. But we're still going to need a
jumping-off page that is handled by Forrest (which is what javadoc.html does
for us) because not all connectors are buildable or can be javadoc'd, depending
on the existence of the needed third-party libraries. If the "api"
subdirectory is the new place where the javadoc roots are all put, that's fine
by me.
> Forrest doc build always gets an error because of relative references to
> javadoc roots
> --------------------------------------------------------------------------------------
>
> Key: CONNECTORS-194
> URL: https://issues.apache.org/jira/browse/CONNECTORS-194
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next
> Reporter: Karl Wright
>
> Forrest is not very happy with generating a relative link to the javadoc
> roots, since the javadoc itself is not under Forrest's control. Somebody
> needs to find a better way of handling this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
