- This topic has 4 replies, 2 voices, and was last updated 20 years, 11 months ago by Scott Anderson.
-
AuthorPosts
-
lukmanphMemberhi guys
am getting this error when i see the configuration file
any idea?Plug-in: “Debug UI” version: “3.0.0” referenced by this feature is not included at runtime. Runtime includes plug-in version “3.6.4” supplied by feature “MyEclipse Core Tooling” version “3.6.4”.
everything works fine except that hot replace does not work, so i figure i has to do with this…
cheers
P
lukmanphMemberam using
myEclipse 3.0.4
eclipse 3.0.4
jdk 1.4.2 b1_06
Scott AndersonParticipantP,
am getting this error when i see the configuration file
Actually, this is a warning (that you can safely ignore) not an error. Since 3.0 is still in flux we had to make a couple minor modifications to the debug plugin to facilitate JSP debugging. Once 3.0 is final we won’t need to do this anymore. In the meantime, our tweaked version of the plugin is supposed to override the normal one, as is being reported.
am using
myEclipse 3.0.4
eclipse 3.0.4
jdk 1.4.2 b1_06I assume you mean MyEclipse 3.6.4 and Eclipse 3.0M4. You stated that hot code replace isn’t working. Can you state specifically what you’re trying to do and what the results are? In addition, can you please post all the information we request in the Posting Guidelines thread? This will help us narrow down the issue much more quickly.
–Scott
MyEclipse Support
lukmanphMemberhi Scott
sorry for the previous lack of info
myEclipse 3.6.4
eclipse 3.0M4
Tomcat 5.12
jdk 1.4.2
Win2000and I have already posted this bug before. the hot code does not work in the sense that it does not reposition the cursor at the beginning of the method when I am modifying it (which is the extent of the changes I do on-fly). I got a warning message stating that JVM was unable to replace code.
so, what i do is just re-trigger my method (by clicking on the browser the app)and it does works with new modification.
that’s why i thought it had to do with the above plugin message.
once again, thanks for your help
P
Scott AndersonParticipantIn all honesty, it’s probably a bit of an imcompatibility between 1.4.2 and the Eclipse debugger. Such things have been reported on the Eclipse newsgroups. Sun has a way of breaking their debug support periodically. 🙂
I doubt you’ll have any problems with JDK 1.4.1, if you’re interested.
–Scott
MyEclipse Support -
AuthorPosts