| Error in exported product log [message #57329] |
Tue, 21 April 2009 09:47  |
Eclipse User |
|
|
|
Hi!
This is x-posted from .equinox, in the hope that you guys might know more
:)
I'm seeing this error in the log of my exported product:
java.io.IOException: Unable to initialize osgi.frameworkClassPath
at org.eclipse.core.launcher.Main.addBaseJars(Main.java:567)
at org.eclipse.core.launcher.Main.getDevPath(Main.java:466)
I solved it using the solution given here:
http://dev.eclipse.org/newslists/news.eclipse.platform.rcp/m sg12468.html
It says:
- Copy the org.eclipse.osgi_vernum.jar from the
plugins/org.eclipse.osgi_vernum directory to the plugins directory
- Delete the org.eclipse.osgi_vernum directory
- Launch the application
So this has solved my problem, but I haven't figured out _why_ I need to
do this. Is there something I can do to prevent it on the Eclipse GUI
side, so it doesn't happen if I'm exporting to a new product?
Thanks!
Maurice
|
|
|
|
| Re: Error in exported product log [message #57658 is a reply to message #57356] |
Wed, 22 April 2009 07:19  |
| Eclipse User |
|
|
|
This was indeed the issue. It's working perfectly now - thanks for your
help!
Maurice
Andrew Niefer wrote:
> It is probably caused by having org.eclipse.osgi imported into your
> workspace as a binary project.
> Try doing the export after closing all such imported binary projects.
> You don't need to have them in your workspace, it is enough that they
> are in your target.
> This would be a bug in the export, but the problem is that from the
> shape of the project, build can't tell that this is a spoofed up bundle
> created by the import and not the real binary bundle.
> Maurice O'Connor wrote:
>> Hi!
>>
>> This is x-posted from .equinox, in the hope that you guys might know
>> more :)
>>
>> I'm seeing this error in the log of my exported product:
>>
>> java.io.IOException: Unable to initialize osgi.frameworkClassPath
>> at org.eclipse.core.launcher.Main.addBaseJars(Main.java:567)
>> at org.eclipse.core.launcher.Main.getDevPath(Main.java:466)
>>
>> I solved it using the solution given here:
>>
>> http://dev.eclipse.org/newslists/news.eclipse.platform.rcp/m sg12468.html
>>
>> It says:
>>
>> - Copy the org.eclipse.osgi_vernum.jar from the
>> plugins/org.eclipse.osgi_vernum directory to the plugins directory
>> - Delete the org.eclipse.osgi_vernum directory
>> - Launch the application
>>
>> So this has solved my problem, but I haven't figured out _why_ I need to
>> do this. Is there something I can do to prevent it on the Eclipse GUI
>> side, so it doesn't happen if I'm exporting to a new product?
>>
>> Thanks!
>>
>> Maurice
>>
>>
>>
|
|
|
| Re: Error in exported product log [message #595977 is a reply to message #57329] |
Tue, 21 April 2009 11:58 |
| Eclipse User |
|
|
|
It is probably caused by having org.eclipse.osgi imported into your
workspace as a binary project.
Try doing the export after closing all such imported binary projects.
You don't need to have them in your workspace, it is enough that they
are in your target.
This would be a bug in the export, but the problem is that from the
shape of the project, build can't tell that this is a spoofed up bundle
created by the import and not the real binary bundle.
Maurice O'Connor wrote:
> Hi!
>
> This is x-posted from .equinox, in the hope that you guys might know
> more :)
>
> I'm seeing this error in the log of my exported product:
>
> java.io.IOException: Unable to initialize osgi.frameworkClassPath
> at org.eclipse.core.launcher.Main.addBaseJars(Main.java:567)
> at org.eclipse.core.launcher.Main.getDevPath(Main.java:466)
>
> I solved it using the solution given here:
>
> http://dev.eclipse.org/newslists/news.eclipse.platform.rcp/m sg12468.html
>
> It says:
>
> - Copy the org.eclipse.osgi_vernum.jar from the
> plugins/org.eclipse.osgi_vernum directory to the plugins directory
> - Delete the org.eclipse.osgi_vernum directory
> - Launch the application
>
> So this has solved my problem, but I haven't figured out _why_ I need to
> do this. Is there something I can do to prevent it on the Eclipse GUI
> side, so it doesn't happen if I'm exporting to a new product?
>
> Thanks!
>
> Maurice
>
>
>
|
|
|
| Re: Error in exported product log [message #596083 is a reply to message #57356] |
Wed, 22 April 2009 07:19 |
| Eclipse User |
|
|
|
This was indeed the issue. It's working perfectly now - thanks for your
help!
Maurice
Andrew Niefer wrote:
> It is probably caused by having org.eclipse.osgi imported into your
> workspace as a binary project.
> Try doing the export after closing all such imported binary projects.
> You don't need to have them in your workspace, it is enough that they
> are in your target.
> This would be a bug in the export, but the problem is that from the
> shape of the project, build can't tell that this is a spoofed up bundle
> created by the import and not the real binary bundle.
> Maurice O'Connor wrote:
>> Hi!
>>
>> This is x-posted from .equinox, in the hope that you guys might know
>> more :)
>>
>> I'm seeing this error in the log of my exported product:
>>
>> java.io.IOException: Unable to initialize osgi.frameworkClassPath
>> at org.eclipse.core.launcher.Main.addBaseJars(Main.java:567)
>> at org.eclipse.core.launcher.Main.getDevPath(Main.java:466)
>>
>> I solved it using the solution given here:
>>
>> http://dev.eclipse.org/newslists/news.eclipse.platform.rcp/m sg12468.html
>>
>> It says:
>>
>> - Copy the org.eclipse.osgi_vernum.jar from the
>> plugins/org.eclipse.osgi_vernum directory to the plugins directory
>> - Delete the org.eclipse.osgi_vernum directory
>> - Launch the application
>>
>> So this has solved my problem, but I haven't figured out _why_ I need to
>> do this. Is there something I can do to prevent it on the Eclipse GUI
>> side, so it doesn't happen if I'm exporting to a new product?
>>
>> Thanks!
>>
>> Maurice
>>
>>
>>
|
|
|
Powered by
FUDForum. Page generated in 0.04068 seconds
Home