| Author |
 Topic  |
|
|
daviddu@cctexas.com
14 Posts |
 Posted - 23 Mar 2006 : 16:52:43
|
BTW: while I'm thinking about it,
The docs in the JAR files are 'hard linked' to specific cross reference locations for a Windows machine.
Since all my development is done on Unix (Solaris, Linux, BSD, ...), they don't work.
Also, Solaris had a fit-and-a-half with those embedded file names that had backslashes in them, when the installer ran. I had to install the software on Linux, massage the paths to get them right, then copy the completed unit to my Solaris system when I was done.
In Eclipse (which I don't use, by the way - only if I want to see the docs), if you open the JavaDocs browser on a particular entry, you can't 'link' to another entry referenced by the docs you initially opened, since the path is hardcoded into the link.
This is probably not something you can fix, but thought you might want to know.
Also, the installer doesn't work extremely well on a non-windows machine. It gets upset if you use a non-DOS path to install.
David |
|
|
quinncurtis
1586 Posts |
Posted - 23 Mar 2006 : 17:40:20
|
Eclipse is creating the links between the javadoc documents automatically. We have no input into the matter. There must be some general Eclipse/Solaris bug creating javadoc on a Windows machine and running them on a Solaris machine.
Does the Javadoc work properly under Linux?
Strange that the software would install under Linux but not Solaris. Sounds like Linux is much more flexible when it comes to pathnames. We wrote the install Setup program in Java; we thought we changed all of the file separators to the system dependent file separator when unzipping, but we could have missed something.
Your comment "Also, Solaris had a fit-and-a-half with those embedded file names that had backslashes ", exactly what embedded file names do you mean ?
What is an example of a non-DOS file name that causes trouble ?
|
 |
|
| |
Topic |
|
|
|
JAVADocs problem
