...> I'm using @link in my javadoc in Netbeans. When I get Netbeans to generate the javadoc it inserts everything correctly but it doesn't...() methodName()} produces "methodName()" in the javadoc {@link #methodName()} produces "#methodName()" in the ... Do I need to tell Netbeans/javadoc to add links? My bad. I... got so many errors in my Javadoc at the moment that I didn'...

... can use them -- this does not work automatically. Because of the above two issues, let me propose a different approach. - All java commands such as /usr/bin/java, javac, javap, javadoc, etc etc are all replaced by a shellscript provided by java-common. The alternatives are removed - There is one 'register' directory managed by java-common where any application providing: a (1) ...

... 2: setting classpath does not happen automatically Because of the above two issues, let me propose a different approach. - All java commands such as /usr/bin/java, javac, javap, javadoc, etc etc are all replaced by a shellscript provided by java-common. The alternatives are removed Regrettably I must state that this would break a very large number of things.... the reason ...

... classpath does not happen automatically Because of the above two issues, let me propose a different approach. - All java commands such as /usr/bin/java, javac, javap, javadoc, etc etc are all replaced by a shellscript provided by java-common. The alternatives are removed Regrettably I must state that this would break a very large number of things.... the ...

...we also add a comment to all JVM post-inst's that selecting this (or any) Java implementation can be done with UJA? - All java commands such as /usr/bin/java, javac, javap, javadoc, etc etc are all replaced by a shellscript provided by java-common. The alternatives are removed Regrettably I must state that this would break a very large number of things.... the reason ...

.... tagsoup.docs: Rename to "docs", following the style of the other files. "tagsoup.txt" seems superfluous, you are installing a manpage anyway. Please consider adding a doc-base file for the JavaDoc. See for example dom4j for how to do this. (Note that the unofficial proposed Java doc-base policy (which you can google for somewhere) prefers the directory name "apidocs" instead of "api",...

Arnaud Vandyck wrote: It's a good idea to remove generated javadoc and jar files and classes. Well, let's agree to disagree. :) They can be removed to use less space and be sure not to include code that has been build with non free dependencies. The space argument is rather weak IMHO, and certainly shouldn't warrant rebuilding a source tarball only for that purpose. (Or do you ...

... upstream release [1]. That advice is plain wrong. (And it's not part of the actual Java policy as the page says.) No, it's not. It's a good idea to remove generated javadoc and jar files and classes. Many Java packages come with jar files for dependencies, i.e. external code where the source is not included in the upstream tarball. Such binaries must be removed and the ...

...> That advice is plain wrong. (And it's not part of the actual Java policy as the page says.) No, it's not. It's a good idea to remove generated javadoc and jar files and classes. Very much so. Unless you build from source, you have no way to know that the binaries correspond to that source code. You can't even guarantee that you're not violating the GPL, which...

On 12/12/06, Marcus Better <marcus@better.se> wrote: Arnaud Vandyck wrote: It's a good idea to remove generated javadoc and jar files and classes. Well, let's agree to disagree. :) ;-) They can be removed to use less space and be sure not to include code that has been build with non free dependencies. The space argument is rather weak IMHO, and certainly shouldn'...