Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IMP » Problems with lpg.runtime and Eclipse 3.4?
Problems with lpg.runtime and Eclipse 3.4? [message #571597] Wed, 25 June 2008 23:17
Eclipse UserFriend
Originally posted by:

Hello All

Thank you all for making this great framework. I am a new user of IMP,
trying to get it running on Eclipse 3.4.0, by following developer's
manual steps. However, I have a few problems, most of which associated
to lpg when running as a plug in:

1) First, when i get project the lpgexe folder is empty
.. Then, I got the executable from lpgdistribution folder and place it
inside project. Is this needed at all?

2) There are 3 run configurations available, and I used
"eclipse-3.2.2-1-L2", is that current? How can I have it on this
workspace without the need to deploy the plug-in every time? Since it
does not come up when I run the eclipse from the workspace normally.

3) Although LPG is available as an external tool in the development
eclipse workspace, it is not, in the workspace I installed the IMP
plugins. Moreover, in the IMP deployed one the lpg.runtime is shown in
the installed plug-ins but could not be found when it is referenced in a
sample project's Maifest file.

4) do I need to get ans deploy the project lpg.runtime.feature?

5) I used to get this error frequently. Although it might have been
cause by my miss-configuration I mention them, may be they help figuring
out the problem:
!ENTRY org.eclipse.ui 4 4 2008-06-24 23:46:44.515
!MESSAGE Could not create action delegate for id:

!ENTRY org.eclipse.equinox.registry 4 1 2008-06-24 23:46:44.515
!MESSAGE Plug-in org.eclipse.imp.metatooling was unable to load class

Hamoun Ghanbari
Previous Topic:Semantic check
Next Topic:LPG executable in Linux
Goto Forum:

Current Time: Mon Sep 24 10:27:34 GMT 2018

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

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

Back to the top