|Re: [Epsilon] Standalone [message #665838 is a reply to message #665490]
||Sat, 16 April 2011 21:10
|| Horacio Hoyos
Registered: October 2009
Here are my findings on how I resolve it, though I don't know if this is a good solution. |
I decided to take a look at the Build Path and Manifest f the EpsilonStandAloneProject. The Build Path showed me that there where some differences in the plugins imported (my project had more of the epsilon plugins). So I went and take a look at the manifest and found that as I wrote the code and solved the missing imports, the eclipse jars where added as "Imports" (single jars, not plugins):
However, in the EpsilonStandalone example Manifest, the plugins where added as "required bundles":
I changed my Manifest to the Epsilon example form and the error was gone.
I am not an eclipse plugins expert and really don't get the difference between the two methods, but google-ing for the error someone suggested a double import could be causing a version discrepancy, or an attempt to modify a core java functionality. I guess the Required-Bundle approach resolves better the dependencies and prevents this error form poping.
Horacio Hoyos Rodriguez
University Of York
Powered by FUDForum
. Page generated in 0.02462 seconds