I see ... I've been accessing the docs from the various DUCC web
servers. Putting HTML in the [root]/docs directory is relatively recent
so I'd missed the directory mismatch. Fixed.
Jim
On 1/16/14 2:40 PM, Marshall Schor wrote:
On 1/16/2014 1:49 PM, Jim Challenger wrote:
On 1/15/14 5:02 PM, Marshall Schor wrote:
fixups for the documentation:
1) Link in duccbook to javadocs has a typo, and is therefore broken; it's
written ... docs/d/apidocs/index.html, but should be ... docs/d/api/index.html
Marshall, the link isn't broken, I just tested it and I got to it just fine!
Where are you looking?
I took the binary distribution artifact and untarred it. It produced a
directory structure:
docs/d/api/ ...
There is no apidocs directory.
-Marshall
2) Submit command, --specification : has:
This file may then be used to submit the job (rather than providing all the
parameters directory to submit).
should be
This file may then be used to submit the job (rather than providing all the
parameters directly to submit)
3) The webpage setup produced by the build for the html duccbook result in the
Chrome browser "forgetting" where it was: If you click on a link that takes you
to some other spot in the documentation (which works), and then you press the
back button, it goes to the top of the file, instead of going back to where it
was. Firefox seems to be OK.
Chrome too, works OK (e.g, it remembers where links came from) on other pages
generated with other tools, such as the uima.apache.org web site. I couldn't
figure out why it didn't work on the duccbook file.
Sounds like a bug in Chrome ! Works fine also in Safari and Opera.
-Marshall
