Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IMP » Eclipse 3.3.0 report
Eclipse 3.3.0 report [message #568638] Fri, 26 October 2007 14:50
Martin Schnabel is currently offline Martin SchnabelFriend
Messages: 17
Registered: July 2009
Junior Member
Hi there,
I am a student very interested in IMP. I working on a small project for
ActionScript 2 and now 3 (ASDT) as a hobby.

"IMP doesn't quite work under Eclipse 3.3 as of yet. We .. encourage
people to pitch in by doing things like testing IMP under 3.3 and
submitting bug reports, if not submitting patches."

I think working in 3.3 saves lots of time because of Mylyn and I also
think its also a great tool too encourage community and participations (I
love the context and focus). So I try to identify some problems an maybe
some solutions.

I run Ubuntu 7.10 with java-6-sun- JVM and Eclipse 3.3.0 as a test
Platform with code from today's head rev. I also evaluated IMP with WinXP
on Eclipse 3.2.2. As long as there is no bugzilla component for IMP I just
put it here.

-- missing HTMLTextPresenter
org.eclipse.imp.editor.UniversalEditor uses
org.eclipse.jdt.internal.ui.text.HTMLTextPresenter that moved to
org.eclipse.jface.internal.text.html.HTMLTextPresenter but is not
accessible because of plugin package restrictions (internal..)

In this case one can easily add the HTMLTextPresenter and the four
required Readers to the IMP codebase (same license).

-- invalid thread access on start-up
That is very easy fixed by wrapping the language registration in a
Runnable executed by the default display in

org.eclipse.swt.SWTException: Invalid thread access

-- (minor) default key binding conflict with subversive
ALT+CTRL+R is set to org.eclipse.imp.xform.findReplace and

-- getAllPlugins()
org.eclipse.pde.internal.core.PluginModelManager.getAllPlugi ns is missing.
however there is a method getAllModels() with the same return type. no
solution because of the next problem.

-- use of internal packages
org.eclipse.imp.metatooling (especially org.eclipse.imp.extensionsmodel)
are using classes in the package org.eclipse.pde.internal.core. The
problem is internal should not be used by others. Since 3.3 Eclipse
started to use OSGi enforced package restriction. That means if not
explicit exported, the package will be inaccessible from other plug-ins.
Maybe this can be resolved by using the corresponding public interfaces
and a custom implementation. But I stop right here for today, I obviously
cant test any of the wizards without the extensionsmodel working.

Best regards
Martin Schnabel
Previous Topic:Some more queries @ IMP!
Next Topic:Missing IMP projects available
Goto Forum:

Current Time: Mon May 21 19:00:36 GMT 2018

Powered by FUDForum. Page generated in 0.02171 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top