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
I would propose to use "ipf-src" instead of "ipf-repo-link" --- simply because it's shorter.
Could it be possible to adapt generation of javadocs (i mean not the {ipf-javadoc} macro, but the javadocs per se) in the way that links to sources would lead to github instead of open-repo? Today, when I open this javadoc and click on the class name, I get redirected to this source.
On Fri, Sep 16, 2011 at 10:44 AM, Dmytro Rud < [email protected]>wrote:
I would propose to use "ipf-src" instead of "ipf-repo-link" --- simply
because it's shorter.
Could it be possible to adapt generation of javadocs (i mean not the
{ipf-javadoc} macro, but the javadocs per se) in the way that links to
sources would lead to github instead of open-repo? Today, when I open [this
javadoc|
http://repo.openehealth.org/sites/ipf/reports/ipf-2.3-m1/apidocs/index.html?org/openehealth/ipf/platform/camel/ihe/mllp/core/intercept/MllpCustomInterceptor.html]
and click on the class name, I get redirected to [this source|
It could be something like:
{ipf-repo-link}org.openehealth.ipf.platform.camel.ihe.pixpdqv3.PixPdqV3CamelTranslators{ipf-repo-link}
Tip: See the code from the existing {ipf-javadoc} macro.
Link to methods and properties: Currently there is no way to link to methods and properties (except the line)
The text was updated successfully, but these errors were encountered: