[craig.stallwood]

I would like to be able to set the JavaDoc location for the MyEclipse J2EE jars, as you can with the standard J2SE, but for some reason when I press OK the location is not saved and no error message is displayed. I am using Eclipse 3.1.1 and MyEclipse 4 on Mac OS X Tiger.

I have tried pointing the javadoc to the online version, and downloading them, but still it does not seem to store them.

Am I doing something wrong?

[Riyad Kalla]

craig,
can you walk me through step by step so I can reproduce this locally?

[innogate]

Having the same problem. My steps are:
– Choose the J2EE 1.3 Library container in Package Explorer and expand it
– Right-click javax.servlet.jar and choose menu item “Properties”
– In field “Javadoc location path” enter “http://java.sun.com/j2ee/sdk_1.3/techdocs/api”
– Click ok
– Open the jar properties again to see: Field is still empty

[Riyad Kalla]

Guys I was able to reproduce this easily, I will file this right away, thanks.

[steveknaus]

I am having the same problem. I try to configure the javadoc and source code locations for jars in “J2EE 1.4 Library Container” and they aren’t being retained.

Any new information about this problem? Is there a suggested workaround? It would be ideal if Genuitec would deliver the javadoc and source for their pre-configured library containers.

I really want to be able to view javadoc and source code for J2EE just like I already can for J2SE.

I’m using MyEclipse 4.0.1 GA, and Eclipse 3.1.0.

[Riyad Kalla]

Steve,
I”m sorry to say the bug hasn’t been addressed yet, I just requested it be reevaluated for possible inclusion into a release soon.

As a temporary workaround, what you can do is not use the Library Set we ship, and instead create your own User Library with the same JARs and attach Javadoc to them. We appologize for the inconvenience.

[steveknaus]

Thank you for your prompt response. I’ll create and configure my own User Library as a workaround.

[Greg Lindholm]

Any update on this?
I just installed ME 4.1GA with Eclipse 3.1.1 and I can’t attach javadocs to J2EE 1.4 library container.
Is there a bug or tracking number?

[Riyad Kalla]

Sorry our bug tracker is not public, but we appologize for this slipping into 4.1, I will add a reminder to get it fixed soon.

[stoeckle]

I’m interested as well! thx!

[Cogni]

I tried the same thing with the newest 5.0M1 (Eclipse 3.2RC7 Build: I20060602-1317) and now this problem causes an error message in a pop-up window:

An error occured while associating the source
org.eclipse.jdt.internat.ui.wizards.buildpaths.BuildPathSupport$UpdatedClasspathContainer

I have NOT tried to define a source attachment, I have tried to set the Javadoc location!!
Seems that there is really a bug inside.

[Riyad Kalla]

I confirmed this trying to attach source, I’ll ping the dev team on this.

[Javier]

Hi guys, I got the same problem with Version: 5.0.0. Is this problem in the dev scope or planned for futures releases?. I love the tool so o want to know if its better to configure the path like you suggest in the workaround or wait to the “patch”.

Regards,
——————-
Keep it simple….

[Riyad Kalla]

This just slipped under the devs radar, I’m flagging it as priority 1 because it’s embaressing.

[dthompson]

I’m running 5.1.0 GA, build id is 20061111-5.1.0-GA and am seeing this problem as well. Any chance this is going to get fixed (ever)? I work in a team environment where we use CVS, and its not going to be acceptable to add our own J2EE library.

[Author]

Posts