Home » Archived » Visual Editor (VE) » Can not add SWT library to project
|
| Re: Can not add SWT library to project [message #57947 is a reply to message #57923] |
Sat, 28 August 2004 17:46   |
Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
I don't know why you are getting this. That method is definitely in that
M2 driver.
1) From your workspace, select Help->About Eclipse->Feature Details and
select the "Java EMF Model" feature, and look at the bottom of the
dialog. The build id listed should be 200407301410
2) go into your installation on disk to
eclipse/plugins/org.eclipse.jem.proxy_1.0.0, in there the proxy.jar
should be listed as 7/30/2004 2:15PM, size 73,994
--
Thanks, Rich Kulp
|
|
|
| Re: Can not add SWT library to project [message #57971 is a reply to message #57947] |
Sat, 28 August 2004 20:32 |
 Jonas Rathert
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
Hi,
Rich Kulp wrote:
> I don't know why you are getting this. That method is definitely in that
> M2 driver.
Actually, I can find the class in one of the JAR files, and the method
seems to be there, yes.
> 1) From your workspace, select Help->About Eclipse->Feature Details and
> select the "Java EMF Model" feature, and look at the bottom of the
> dialog. The build id listed should be 200407301410
No it is not: as mentioned in my first post it is 200406281448. Which is
strange as the files (e.g. proxy.jar) in my eclipse directory are from
20040730 - which answers your second question:
> 2) go into your installation on disk to
> eclipse/plugins/org.eclipse.jem.proxy_1.0.0, in there the proxy.jar
> should be listed as 7/30/2004 2:15PM, size 73,994
It is 7/30/2004 2:16PM, size 73,994. - quite the same :-)
But your answer led me to the right direction: As I mentioned before, I
also use the MyEclipse software (a bundle of various plugins) an they also
ship JEM (and GEF, btw). The funny thing is that eclipse finds the
feature in $ECLIPSE_HOME\features, but the plugin shipped with MyEclipse
(which is installed in a different directory!) is used!?
I do not understand how eclipse finds and loads features and plugins, but
I removed the JEM and GEF plugins that came with MyEclipse and everything
seems to work (at least loading the SWT lib in VEP works, I could not yet
test all MyEclipse functionality :-).
BTW: Before the import via "Add Library..." worked, I tried it by adding
swt.jar "manually" (via "Add External JARs...") - but this did not help!
Can you shortly explain the difference between "Add Library" and "Add
External JARs"?
Anyway, case closed. Thanks for your fast help!
Kind regards,
Jonas
--
Note: 96.31% of all statistics are fiction.
|
|
|
| Re: Can not add SWT library to project [message #57995 is a reply to message #57971] |
Mon, 30 August 2004 15:00 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
We need to know SWT is available. Also, since we need to start a remote
vm with SWT in it for us to get the pictures of what you are building,
we need to also add in the appropriate dlls. Just adding swt.jar to the
classpath doesn't do this. The SWTContainer that we wrote does all of
these things. It tells us that SWT is loaded, it tells us that we need
to add in the dlls to library path, it tells us to load the SWT palette
category.
--
Thanks, Rich Kulp
|
|
|
| Re: Can not add SWT library to project [message #597901 is a reply to message #57923] |
Sat, 28 August 2004 17:46 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
I don't know why you are getting this. That method is definitely in that
M2 driver.
1) From your workspace, select Help->About Eclipse->Feature Details and
select the "Java EMF Model" feature, and look at the bottom of the
dialog. The build id listed should be 200407301410
2) go into your installation on disk to
eclipse/plugins/org.eclipse.jem.proxy_1.0.0, in there the proxy.jar
should be listed as 7/30/2004 2:15PM, size 73,994
--
Thanks, Rich Kulp
|
|
|
| Re: Can not add SWT library to project [message #597908 is a reply to message #57947] |
Sat, 28 August 2004 20:32 |
Jonas Rathert
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
Hi,
Rich Kulp wrote:
> I don't know why you are getting this. That method is definitely in that
> M2 driver.
Actually, I can find the class in one of the JAR files, and the method
seems to be there, yes.
> 1) From your workspace, select Help->About Eclipse->Feature Details and
> select the "Java EMF Model" feature, and look at the bottom of the
> dialog. The build id listed should be 200407301410
No it is not: as mentioned in my first post it is 200406281448. Which is
strange as the files (e.g. proxy.jar) in my eclipse directory are from
20040730 - which answers your second question:
> 2) go into your installation on disk to
> eclipse/plugins/org.eclipse.jem.proxy_1.0.0, in there the proxy.jar
> should be listed as 7/30/2004 2:15PM, size 73,994
It is 7/30/2004 2:16PM, size 73,994. - quite the same :-)
But your answer led me to the right direction: As I mentioned before, I
also use the MyEclipse software (a bundle of various plugins) an they also
ship JEM (and GEF, btw). The funny thing is that eclipse finds the
feature in $ECLIPSE_HOME\features, but the plugin shipped with MyEclipse
(which is installed in a different directory!) is used!?
I do not understand how eclipse finds and loads features and plugins, but
I removed the JEM and GEF plugins that came with MyEclipse and everything
seems to work (at least loading the SWT lib in VEP works, I could not yet
test all MyEclipse functionality :-).
BTW: Before the import via "Add Library..." worked, I tried it by adding
swt.jar "manually" (via "Add External JARs...") - but this did not help!
Can you shortly explain the difference between "Add Library" and "Add
External JARs"?
Anyway, case closed. Thanks for your fast help!
Kind regards,
Jonas
--
Note: 96.31% of all statistics are fiction.
|
|
|
| Re: Can not add SWT library to project [message #597912 is a reply to message #57971] |
Mon, 30 August 2004 15:00 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
We need to know SWT is available. Also, since we need to start a remote
vm with SWT in it for us to get the pictures of what you are building,
we need to also add in the appropriate dlls. Just adding swt.jar to the
classpath doesn't do this. The SWTContainer that we wrote does all of
these things. It tells us that SWT is loaded, it tells us that we need
to add in the dlls to library path, it tells us to load the SWT palette
category.
--
Thanks, Rich Kulp
|
|
|
Goto Forum:
Current Time: Thu Dec 26 12:19:01 GMT 2024
Powered by FUDForum. Page generated in 0.04082 seconds |
] 
Search
Help
Register
Login
Home
