Is it worth adding automatic support for javadoc linking? For example, if you had the following in a post:
org.gradle.api.tasks.Copy#setDestinationDir(java.io.File) It would become: <a href="http://gradle.org/current/docs/javadoc/org/gradle/api/tasks/Copy.html#setDestinationDir(java.io.File)">Copy#setDestination(java.io.File)</a> Or just: org.gradle.api.tasks.Copy would become <a href="http://gradle.org/current/docs/javadoc/org/gradle/api/tasks/Copy.html";>Copy</a> One problem with this would be that we don't know what is Groovydoc and what is Javadoc. We could maybe use a g: prefix or something along those lines if we wanted to differentiate. It wouldn't take long to implement. Would it be worth it? -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
