search

ollie314 / hamcrest

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

Publish javadocs #81

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
It would be useful if javadocs from the hamcrest-java artifacts were
published in permanent locations that they could be linked to. For example,
javadoc external links as configured in the maven-javadoc-plugin [1].
Currently, one has to link JUnit, JMock or other instead just to link into
hamcrest javadoc.

[1]
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#links

Original issue reported on code.google.com by estebis...@gmail.com on 12 May 2009 at 2:17

GoogleCodeExporter commented 8 years ago 
Concur.

Original comment by dancerj...@gmail.com on 14 Sep 2011 at 10:44

GoogleCodeExporter commented 8 years ago 
tagging

Original comment by t.denley on 12 May 2012 at 10:55

GoogleCodeExporter commented 8 years ago 
JavaDoc is now available here:

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

Original comment by t.denley on 1 Sep 2012 at 12:31

GoogleCodeExporter commented 8 years ago 
t.denley's link is dead as of January 2013.

Original comment by a...@gurdasani.com on 21 Jan 2013 at 5:32

GoogleCodeExporter commented 8 years ago 
This latest fail isn't specific to hosted javadoc, the whole of 
http://hamcrest.org/ is down.

This is hosted on GitHub pages, so I'll check their status. Might be a dns 
issue.

Original comment by t.denley on 21 Jan 2013 at 5:51

GoogleCodeExporter commented 8 years ago 
GitHub pages status is good -- https://status.github.com/

Turns out the domain resolution is broken. I've sent an email to the person who 
handles this.  Will update when I hear back.

Original comment by t.denley on 21 Jan 2013 at 5:59

GoogleCodeExporter commented 8 years ago 
Great the email for the owner has just bounced because his personal domain 
isn't resolving either.  I'm guessing his registrar is having issues (or he 
forgot to pay the bills)... I'll keep digging.

Original comment by t.denley on 21 Jan 2013 at 6:02

GoogleCodeExporter commented 8 years ago 
Right, I think I've got to the bottom of this.  Seems like DreamHost are having 
some issues: 
http://www.dreamhoststatus.com/2013/01/20/apache-issues-in-los-angeles-datacente
r/

Hopefully should be fixed soon.

Original comment by t.denley on 21 Jan 2013 at 6:08

GoogleCodeExporter commented 8 years ago 
All seems to be working now.

Original comment by t.denley on 22 Jan 2013 at 8:05