|
|
|
|
|
|
|
| Re: Feature based app is exporting fine but not starting with exit code -1 [message #67856 is a reply to message #67796] |
Fri, 10 July 2009 11:30  |
Eclipse User |
|
|
|
There is a bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=240821.
The workaround is not have the imported binary projects in your
workspace when you do the export. Build will find them in the target.
-Andrew
Philipp Kursawe wrote:
> Chris Aniszczyk wrote:
>> Philipp Kursawe wrote:
>>> Exception in thread "main" java.lang.NoClassDefFoundError:
>>> org/eclipse/equinox/launcher/JNIBridge
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.eclipse.equinox.launcher.JNIBridge
>
> I found the reason for it!
> I had imported all the required bundles from the target platform as
> binary plugins into my workspace. So I could test a feature based run
> configuration inside the IDE. Well, it seems that it does not work for 2
> reasons. One seems to be that, even though they are supposed to be
> binary projects, they contain a *source.jar and the code of the plugin
> inside another *jar INSIDE the actual plugin.jar. And the classpath was
> wrong in all target platform imported plugins. PDE or whoever is
> responsible for importing plugins into the workspace does it wrong. You
> end up with a launcherXXX.jar plugin that contains a launcher.src.jar
> and a launcher.jar but the classpath in the manifest is not adjusted to
> point to launcher.jar INSIDE the plugin. For whatever reason the
> exporter/importer decides to repackage the plugin instead of just
> copying it from the target platform.
>
> I hope I made clear what goes wrong. If not I will post such a damaged
> exported plugin.
>
> Thats how the plugin looks like after the import (using Import wizard
> with BINARY plugin option):
> http://screencast.com/t/t1R5yRTw6
>
>
> Any ideas?
> Phil
|
|
|
|
| Re: Feature based app is exporting fine but not starting with exit code -1 [message #599178 is a reply to message #67693] |
Thu, 09 July 2009 14:10 |
| Eclipse User |
|
|
|
Chris Aniszczyk wrote:
> Philipp Kursawe wrote:
>> Hello,
>>
>> beside my feature based RCP app not able to run inside 3.5 anymore it
>> also has problems when exported. It exports fine but is not startable.
>> The error message is visible here:
>> http://screencast.com/t/Kr4Lr65dOh
>>
>> Even Deltapacks are in the target platform.
>>
>> I have no idea what that means.
>
> Do you have some logs generated anywhere in the metadata area? There
> isn't much to go on here... mostly signifies that a problem has happened
> very early in the launching process (ie., maybe not pointing to the
> proper osgi jar etc...)
Unfortunatly nothing is logged. Not even a workspace is generated. The
thing is, on an older I-Build of 3.5 the export works and the RCP app
runs. I will keep you updated.
Phil
|
|
|
| Re: Feature based app is exporting fine but not starting with exit code -1 [message #599186 is a reply to message #67693] |
Thu, 09 July 2009 14:33 |
| Eclipse User |
|
|
|
Chris Aniszczyk wrote:
> Philipp Kursawe wrote:
>> Hello,
>>
>> beside my feature based RCP app not able to run inside 3.5 anymore it
>> also has problems when exported. It exports fine but is not startable.
>> The error message is visible here:
>> http://screencast.com/t/Kr4Lr65dOh
>>
>> Even Deltapacks are in the target platform.
>>
>> I have no idea what that means.
>
> Do you have some logs generated anywhere in the metadata area? There
> isn't much to go on here... mostly signifies that a problem has happened
> very early in the launching process (ie., maybe not pointing to the
> proper osgi jar etc...)
Here is the output when i start with -console:
Exception in thread "main" java.lang.NoClassDefFoundError:
org/eclipse/equinox/launcher/JNIBridge
Caused by: java.lang.ClassNotFoundException:
org.eclipse.equinox.launcher.JNIBridge
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
Exception in thread "main" java.lang.NoClassDefFoundError:
org/eclipse/equinox/launcher/Main
Caused by: java.lang.ClassNotFoundException:
org.eclipse.equinox.launcher.Main
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
Exception in thread "main" java.lang.NoClassDefFoundError:
org/eclipse/equinox/launcher/Main
Caused by: java.lang.ClassNotFoundException:
org.eclipse.equinox.launcher.Main
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
|
|
|
|
| Re: Feature based app is exporting fine but not starting with exit code -1 [message #599201 is a reply to message #67755] |
Thu, 09 July 2009 18:25 |
| Eclipse User |
|
|
|
Chris Aniszczyk wrote:
> Philipp Kursawe wrote:
>> Exception in thread "main" java.lang.NoClassDefFoundError:
>> org/eclipse/equinox/launcher/JNIBridge
>> Caused by: java.lang.ClassNotFoundException:
>> org.eclipse.equinox.launcher.JNIBridge
>
> This usually signifies a launcher fragment can't be found properly.
Chris, the fragment for win32 x86 is there, its unpacked in plugins.
The loader wants to load win32 x86, and even with deltapack installed
its no change.
I am little confused here, as it was working 2 days ago without any
updates happened to the target platform meanwhile.
Phil
|
|
|
| Re: Feature based app is exporting fine but not starting with exit code -1 [message #599206 is a reply to message #67755] |
Thu, 09 July 2009 18:47 |
| Eclipse User |
|
|
|
Chris Aniszczyk wrote:
> Philipp Kursawe wrote:
>> Exception in thread "main" java.lang.NoClassDefFoundError:
>> org/eclipse/equinox/launcher/JNIBridge
>> Caused by: java.lang.ClassNotFoundException:
>> org.eclipse.equinox.launcher.JNIBridge
I found the reason for it!
I had imported all the required bundles from the target platform as
binary plugins into my workspace. So I could test a feature based run
configuration inside the IDE. Well, it seems that it does not work for 2
reasons. One seems to be that, even though they are supposed to be
binary projects, they contain a *source.jar and the code of the plugin
inside another *jar INSIDE the actual plugin.jar. And the classpath was
wrong in all target platform imported plugins. PDE or whoever is
responsible for importing plugins into the workspace does it wrong. You
end up with a launcherXXX.jar plugin that contains a launcher.src.jar
and a launcher.jar but the classpath in the manifest is not adjusted to
point to launcher.jar INSIDE the plugin. For whatever reason the
exporter/importer decides to repackage the plugin instead of just
copying it from the target platform.
I hope I made clear what goes wrong. If not I will post such a damaged
exported plugin.
Thats how the plugin looks like after the import (using Import wizard
with BINARY plugin option):
http://screencast.com/t/t1R5yRTw6
Any ideas?
Phil
|
|
|
| Re: Feature based app is exporting fine but not starting with exit code -1 [message #599233 is a reply to message #67796] |
Fri, 10 July 2009 11:30 |
| Eclipse User |
|
|
|
There is a bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=240821
The workaround is not have the imported binary projects in your
workspace when you do the export. Build will find them in the target.
-Andrew
Philipp Kursawe wrote:
> Chris Aniszczyk wrote:
>> Philipp Kursawe wrote:
>>> Exception in thread "main" java.lang.NoClassDefFoundError:
>>> org/eclipse/equinox/launcher/JNIBridge
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.eclipse.equinox.launcher.JNIBridge
>
> I found the reason for it!
> I had imported all the required bundles from the target platform as
> binary plugins into my workspace. So I could test a feature based run
> configuration inside the IDE. Well, it seems that it does not work for 2
> reasons. One seems to be that, even though they are supposed to be
> binary projects, they contain a *source.jar and the code of the plugin
> inside another *jar INSIDE the actual plugin.jar. And the classpath was
> wrong in all target platform imported plugins. PDE or whoever is
> responsible for importing plugins into the workspace does it wrong. You
> end up with a launcherXXX.jar plugin that contains a launcher.src.jar
> and a launcher.jar but the classpath in the manifest is not adjusted to
> point to launcher.jar INSIDE the plugin. For whatever reason the
> exporter/importer decides to repackage the plugin instead of just
> copying it from the target platform.
>
> I hope I made clear what goes wrong. If not I will post such a damaged
> exported plugin.
>
> Thats how the plugin looks like after the import (using Import wizard
> with BINARY plugin option):
> http://screencast.com/t/t1R5yRTw6
>
>
> Any ideas?
> Phil
|
|
|
Powered by
FUDForum. Page generated in 0.07174 seconds
Home