Introduce Javadoc and source when using eclipse

Function

With eclipse, you can easily view the source code and help documentation of the referenced third-party jar package, which not only improves the development efficiency, but also contributes to our learning and progress.

The method provided by this website is recommended: http://blog.csdn.net/cjjky/article/details/6535426. On the basis of this method, note the following: the source code does not need to be decompressed and imported. For the source code of the corresponding jar package, you do not need to decompress the package before importing and viewing the package. In the project development source code, you can also select the. Jar format source code or the decompressed folder. The three selection buttons on the right are: Workspace: directly select the foleror. Zip/. jar file with source code from the workspace; external file: select the .zip/. jar file with source code from the external interface; external Folder: select the folder with source code from the external world. The second option on the left is to select the attached javadoc. The first method is javadoc URL. You can directly enter the URL and view the API through the Internet, you can also Click Browse to select the help document (API ). The following validate button is used to test whether the API documentation is available. It should be noted that for the pop-up dialog box after detection, the result of the open in browser on the right is incorrect, that is, even if the setting is successful, but it cannot be opened in external browsers, so you don't have to worry about it. The second method is javadoc in archive, which is used to select the. Zip/examples/. jar file. After setting, you can directly view the source code and API of the third-party jar package in eclipse, click the corresponding class or method, and press the shortcut key F1 to open the help view and view the API. Be sure to find the jar package that requires setting Javadoc and source. When I first set the jar package, I always did not respond. Check that the set path is completely correct, and finally I will reflect it. For third-party. jar package, first copied to the Lib folder, at this time, the corresponding jar package has been generated in the web app libraries, you do not need to build path again, but I build path again, which is required in Android, but not in Java ee. After creating the path, duplicate jar packages will appear in libraries, but these jar packages will not be used, however, I am setting source and javadoc for jar packages that will not be used, so it is always unsuccessful. This reminds you that it is a waste of time to avoid making the same mistake as me. That's it. I hope it will help you! Supplement: To import JDK Javadoc and source, import the Rt. jar package.