|java.lang.NoClassDefFoundError in Plugin [message #55613]
||Thu, 16 April 2009 10:36
| Timothy Marc
Registered: July 2009
me and some guys from the institute have investigated some common,
probable issues or faults, but we still get the NCDF-Error, after
exporting out plugins as features and installing them into another
eclipse instance (both 3.4 releases).
The class, which is not found is exported and still present in the
exported plugin, as well as its package is exported in the runtime
section of MANIFEST.MF. We still have cleaned, reexported etc. the whole
scenario, but after exporting the feature, the class won't be found.
Even if we create a new, cleaned workspace, we have no success. From
inside the development ide or by debugging it by running an Eclipse
Application, it works! Very strange.
Here is the stack trace:
de.fraunhofer.fokus.testing.transformation.modelplex.sys2pit .Sys2PITTransformator.iterateTestContextModels(Sys2PITTransf ormator.java:186)
de.fraunhofer.fokus.testing.transformation.modelplex.sys2pit .Sys2PITTransformator.transform(Sys2PITTransformator.java:13 7)
de.fraunhofer.fokus.testing.transformation.gui.importWizards .TestingFileImportWizard.performFinish(TestingFileImportWiza rd.java:48)
Any ideas, we have no more :(
|Re: java.lang.NoClassDefFoundError in Plugin [message #56217 is a reply to message #55774]
||Thu, 16 April 2009 17:36
Originally posted by: tmothymarc.freenet.de|
Okay, thanks for this hint. It works now ;-)
Ankur Sharma schrieb:
> Timothy Marc wrote:
>> Currently, we're copying the files into the target platform directories.
>> Ankur Sharma schrieb:
>>> Timothy Marc wrote:
>>>> exporting out plugins as features and installing them into another
>>>> eclipse instance (both 3.4 releases).
>>> How are you installing it to another eclipse? Export -> Install into
>>> host. Repository?
>>> Another way to do the same thing could be by creating an update site.
> 3.4 have P2 provisioner to handle installing/updating the plugins. The
> 3.3 way of copying the plugins to eclipse\plugins won't work. You need
> to drop them to eclipse\dropins location. The recommended way to go
> about it would to build an update site. And update you other eclipse
> installation using it.
Powered by FUDForum
. Page generated in 0.02641 seconds