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
In the case where the Javadoc of a project is hosted alongside the documentation via HTML backend (for instance via a Maven site), relative URIs work well to link from the userguide to the corresponding version of the Javadoc:
org.acme=./apidocs/
But when the Asciidoctor backend is standalone (pdf, confluence page, ...), the URIs need to become absolute:
org.acme=http://myserver/myproject/apidocs/
Rather than using 2 apidocs.properties files and having some duplication, the feature would be to have a new attribute apidocs_baseuri that could be set only for the standalone backends in order to automatically prefix the relative URIs:
In the case where the Javadoc of a project is hosted alongside the documentation via HTML backend (for instance via a Maven site), relative URIs work well to link from the userguide to the corresponding version of the Javadoc:
org.acme=./apidocs/
But when the Asciidoctor backend is standalone (pdf, confluence page, ...), the URIs need to become absolute:
org.acme=http://myserver/myproject/apidocs/
Rather than using 2 apidocs.properties files and having some duplication, the feature would be to have a new attribute apidocs_baseuri that could be set only for the standalone backends in order to automatically prefix the relative URIs:
The text was updated successfully, but these errors were encountered: