You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This nice little service http://javadoc.io/ could be used to render our javadocs, but there are multiple jars per project. So there are 2 choices:
Make a new page in each project's documentation that lists links to all javadocs, one per jar
Publish an aggregate jar and make it appear in http://javadoc.io/. For that to work we'd have to know a little bit about the internals of the service (does it support this kind of aggregation?).
Option 1 is easier for us, but option 2 is more convenient for users.
The text was updated successfully, but these errors were encountered:
I think a variant of option 2 will work (cf http://javadoc.io/doc/org.springframework.cloud/spring-cloud-commons-parent/1.1.4.RELEASE). The parent project can aggregate javadocs and publish them as a single jar. The only tricky thing is then knowing the name of the parent project, but users will never need to care, if they just follow links from the home page. Here's what I used to create the spring-cloud-commons-parent docs:
This nice little service http://javadoc.io/ could be used to render our javadocs, but there are multiple jars per project. So there are 2 choices:
Option 1 is easier for us, but option 2 is more convenient for users.
The text was updated successfully, but these errors were encountered: