- This topic has 4 replies, 3 voices, and was last updated 19 years, 11 months ago by Riyad Kalla.
-
AuthorPosts
-
YellowDogMemberIn the J2EE Library Container, for javax.servlet.jar, I set the Javadoc to file:/%TOMCAT_HOME%/webapps/tomcat-docs/servletapi/. (Note: substitute the Tomcat 5.0 install directory for %TOMCAT_HOME%). Now in the Java editor (regardless of view), when I mouse over a class or method belonging to the javax.servlet package, all I get is the fully-qualified class or method name. If I select the element and hit F2, same thing. If I select and hit Shift-F2, full Javadoc comes up in Eclipse’s Help window, as expected. Setting the Javadoc similarly for JRE System Library (rt.jar) – no problems – everything works as expected. Am I missing something?
Riyad KallaMemberThe librarysets in MyEclipse were implemented as a solution for the Eclipse 2.x stream of code. Since Eclipse 3.0M8 Library Sets are actually part of the platform and in a future release of MyEclipse will consolidate our efforts based on what the new Eclipse 3.0 platform gives us.
We appologize for the inconvenience as it stands now, the only work around I can think of off the top of my head is to manually add the servlet-api.jar and jsp-api.jar files from Tomcat, and connect the Tomcat docs to them (this is what I do).
Pierre-Antoine GrégoireMemberUP !!! is this corrected in version 3.8.3???
Pierre-Antoine GrégoireMemberI find it annoying not to be able to launch “Generate javadoc…” properly on a web project.
Or is there any way to customize the web project templates in order to remove the library sets and directly put the libraries or Eclipse 3 library sets?Thanks in advance.
Riyad KallaMemberzepaq,
This is an inherent problem of using Library Sets (Eclipse concept) and trying to run an external process from Eclipse (Ant) and hoping that it picks up the environment settings of Eclipse. You can manually edit the Generate Javadoc Ant script and add a classpath entry that points to the JARs that are in the Library Sets that you need in your build path; other than that I am not aware of a better way to share your environment across the Eclipse/Ant execution boundry. -
AuthorPosts