ollie314 / hamcrest

Automatically exported from code.google.com/p/hamcrest
0 stars 0 forks source link

Link to "current" doc #197

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Please provide a link to the "current" Javadoc.

http://hamcrest.org/JavaHamcrest/javadoc/current/

which would point to (as of April 2013):

http://hamcrest.org/JavaHamcrest/javadoc/1.3/

Original issue reported on code.google.com by sebastia...@gmail.com on 20 Apr 2013 at 8:11

GoogleCodeExporter commented 8 years ago
I don't quite understand the use for this.  Do you not want to link to the 
JavaDoc for the specific version of Hamcrest that you are using?  I don't 
believe that it is standard practice to have a floating link for JavaDoc.

Perhaps you could give some more details of your use-case?

Original comment by t.denley on 22 Apr 2013 at 7:14

GoogleCodeExporter commented 8 years ago
http://junit.sourceforge.net/javadoc/
http://static.springsource.org/spring/docs/current/javadoc-api/
http://docs.guava-libraries.googlecode.com/git-history/release/javadoc/index.htm
l
http://ehcache.org/apidocs/
http://commons.apache.org/proper/commons-lang/javadocs/api-release/
http://logback.qos.ch/apidocs/index.html

Original comment by sebastia...@gmail.com on 22 Apr 2013 at 9:40

GoogleCodeExporter commented 8 years ago
http://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuratio
n.html

Instead of just increasing the dependency version, one also has to remember to 
update the Javadoc Link too.

Original comment by sebastia...@gmail.com on 22 Apr 2013 at 9:42

GoogleCodeExporter commented 8 years ago
Fair enough.

I'll have to look into this, as we host the JavaDoc on gh-pages and I'd rather 
introduce a symlink if possible, rather than copying the entire directory.

If you have the time to investigate whether this is possible, that would speed 
me up.

Original comment by t.denley on 23 Apr 2013 at 7:50