[Panagiotis Korros]

MyEclipse 3.x up to 3.8 beta1 includes a version of the org.eclipse.jdt.debug plugin that replaces the official version.

By doing that we can’t take advantage of the bugfixing done in the official version.

Now that 3.0 is almost out you should try to use the new eclipse infrastructure (JSR-45 debuging etc) and remove the patched org.eclipse.jdt.debug plugin.

[Scott Anderson]

We’re looking at doing this right now and will stop shipping the debug plugins as soon as possible. Please note, however, that we always patch and patch the latest versions so they contain all the bug fixes from Eclipse.

[Panagiotis Korros]

MyEclipse 3.8 Beta2 still contain the patched org.eclipse.jdt.debug plugins. I hope that they will be removed my the time 3.8 becomes final.

[Phillip Beauvoir]

Yes, I agree. I don’t like this:

!SESSION Jul 13, 2004 14:29:44.78 ———————————————-
eclipse.buildId=unknown
java.version=1.4.2_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

!ENTRY org.eclipse.pde.core 1 1 Jul 13, 2004 14:29:44.78
!MESSAGE Problems encountered while PDE was scanning the Target Platform
!SUBENTRY 1 org.eclipse.debug.ui 1 1 Jul 13, 2004 14:29:44.78
!MESSAGE This plug-in (located at “d:\eclipse\plugins\org.eclipse.debug.ui_3.0.0”) was ignored because another version of the same plug-in (located at “D:\eclipse-plugs\MyEclipse\eclipse\plugins\org.eclipse.debug.ui_3.7.200”) was picked
!SUBENTRY 1 org.eclipse.jdt.debug 1 1 Jul 13, 2004 14:29:44.78
!MESSAGE This plug-in (located at “d:\eclipse\plugins\org.eclipse.jdt.debug_3.0.0”) was ignored because another version of the same plug-in (located at “D:\eclipse-plugs\MyEclipse\eclipse\plugins\org.eclipse.jdt.debug_3.7.200”) was picked

PB

[Scott Anderson]

Guys,

This is “mucha ado” about very little. We’ve already stated that we make a few minor mods to two debug plugins to support source level JSP debugging. Until 3.0 final, it was impossible to add this capability without doing that. It appears that now the the last release of 3.0 is out, it may be possible to provide this capability through extensions and we’ll be investigating doing that later this month.

By the way, the entry in the log file simply shows that Eclipse correctly selected our versions of the two plugins rather than the base ones since they are specified as being a later version. It’s the correct behavior and can be safely ignored.

[Phillip Beauvoir]

OK, thanks for the info on this. The only issue then is to ensure that the patched versions stay in synch with Eclipse’s versions – I often have to use Eclipse Integration builds to get over issues.

BTW – MyEclipse support here is superb! 😀

PB

[Scott Anderson]

Phillipus,

The only issue then is to ensure that the patched versions stay in synch with Eclipse’s versions

We update them with every release to be sure they stay in sync. Hopefully, we can find another solution soon.

I often have to use Eclipse Integration builds to get over issues.

Now that 3.0 has gone final, hopefully that will be less the case going forward. 🙂

BTW – MyEclipse support here is superb!

Thanks for that. We all try to do our best. 🙂

[Phillip Beauvoir]

I’m using the latest Eclipse maintenance releases because they fix issues that I rely on. I notice this:

http://download.eclipse.org/downloads/drops/M-M20040721-200407210928/buildnotes/buildnotes_jdt-core.html

where it says:

– Plugin version ID got incremented to 3.0.1.

Will this affect the MyEclipse installation?

PB

[Scott Anderson]

Phillipus,

Shouldn’t be a problem at all.

[Phillip Beauvoir]

@support-scott wrote:

Phillipus,

Shouldn’t be a problem at all.

Nice.

😉

[Author]

Posts