How to make javadoc.jar a priority over javadoc in sources.jar?

Question

I have a limited selection of source code superimposed on the decompiled code in the source bank.

This is great, as it gives me an easy way to deploy code during debugging, however it seems to have a side effect of disabling javadoc from the associated javadoc.jar from working in eclipse, despite the fact that I have a separate javadoc.jar file with javadoc in it.

I assume this is because eclipse finds the "source code" and assumes that all javadoc is in the source, and therefore there is no need to check the javadoc.jar file.

I would like to say eclipse (preferably using maven) so as not to use source.jar for javadoc and use javadoc.jar. I would still like to use source.jar for the source code.

I suggested that eclipse prefers to display javadoc from sources and might be wrong, so please correct me if that is the case.

In addition, I can just do something just wrong, so please let me know if that is the case.

Answer 1

I hunt for the same thing. I have some source jars that I created using jad (and since they are decompiled, they don’t have JavaDoc) and are attached as source attachments. I also have JavaDoc. This seems to be a limitation of Eclipse. It will clear the JavaDoc from the sources and show it (even if it is empty) instead of looking at the JavaDoc. I would like to note that JavaDoc was not in the source code and instead tried the location of JavaDoc. If I don’t find a solution, I will send a question and / or feature request to the Eclipse website.

One way could be integration into a jcom decompiler (for example, jad) the ability to examine both the source of javadoc and return javadoc to the source code. It will also have parameter names for the available methods so that they can be returned. Many of them suggested this, but I cannot find those who did it.

A few caveats. Firstly, jade has not been supported for a long time. The JD-Core / JD-Eclips website has disappeared. And I have not found a better Java decompiler than jad. What happened to all the great gurus and Java decompilation solutions? Secondly, it can be difficult to use the "align for debugging" function to make sure that JavaDoc comments do not take up more space than is available.