These are chat archives for fiji/fiji

3rd
Oct 2017
Curtis Rueden
@ctrueden
Oct 03 2017 20:05
Finally finished this: http://javadoc.scijava.org/
Same thing as javadoc.imagej.net, except that the ImageJ software stack layers are not proxied to jenkins.imagej.net anymore, but rather served by GitHub Pages. So now the old javadoc.imagej.net redirects to it.
And Travis CI keeps those Javadocs up to date.
Philipp Hanslovsky
@hanslovsky
Oct 03 2017 20:06
:plus1:
Curtis Rueden
@ctrueden
Oct 03 2017 20:06
It still uses proxy/reverse-proxy for the 3rd party sites. We could set up Travis CI to rsync stuff daily and commit it, but... maybe that's a little aggressive, I dunno.
SSL cert is not in place yet. Will do that within the next weeks as part of our Dockerization of everything.
As an aside: if you haven't looked at the Java 9 javadocs yet... they are pretty different! Modularized, and if you click Index there is a search bar built in now. Snazzy.
Jan Eglinger
@imagejan
Oct 03 2017 20:37
:+1: :+2: :+3: :smile:
(ImageJ1 javadoc looks broken: http://javadoc.scijava.org/ImageJ1/)
Curtis Rueden
@ctrueden
Oct 03 2017 20:47
ImageJ1 javadoc should be fixed now. Was a typo in the Apache config.
Jan Eglinger
@imagejan
Oct 03 2017 20:49
@ctrueden yep, it's fixed, thanks! Would it be easy to switch it to Frames view by default?
Curtis Rueden
@ctrueden
Oct 03 2017 21:08
@imagejan It is something weird about how Jenkins serves the javadoc. If you go to javadoc/ then there are surprisingly no frames, but javadoc/index.html has them. So the javadoc tool is doing the right thing; Jenkins is just preferring to do something weird with the directory request.
Once we switch ImageJ1 over to the same scheme as all the others, it will be moot, because it won't be served by Jenkins anymore.
The reason I didn't already switch it over is because the ImageJ1-javadoc job was part of some chain of Jenkins jobs, and I was nervous about changing it. But really, it's at the end of that chain, and wouldn't hurt anything to disable. Famous last words.
Curtis Rueden
@ctrueden
Oct 03 2017 21:30
Oh, I guess the other reason I didn't set it up yet is because I haven't moved ImageJ1 over to Travis generally.
It is a workaround for the security policy crap we dealt with before. I think it is not worth grappling with in the short term.