| problem with EclipseStarter [message #56943] |
Tue, 17 January 2006 00:49  |
 David Kemper
Messages: 8
Registered: July 2009 |
Junior Member |
|
|
I'm still using the latest official 3.1.1 Eclipse release with its
Equinox internals, and I'm having issues launching Equinox with the
update configurator.
I apologize for the length of this post. I thought it better to be as
complete as I can. Specifically:
I have the following disk layout.
/root
/plugins
org.eclipse.osgi_3.1.1.jar
org.eclipse.core.runtime_3.1.1.jar
org.eclipse.update.configurator_3.1.0.jar
my.test_1.0.0.jar
In other words, I want my disk layout to mirror that of Eclipse
including, eventually, support for /root/features.
I'm invoking a JVM with a class-path of
/root/plugins/org.eclipse.osgi_3.1.1.jar
I'm setting the system properties: (\+line breaks for formatting)
---start properties
osgi.bundles=\
org.eclipse.core.runtime@1:start,\
org.eclipse.update.configurator@2:start
osgi.configuration.area=\
/root/config
eclipse.ignoreApp=
true
---end properties
I'm using org.eclipse.core.runtime.adaptor.EclipseStarter.main() as my
Java entry point. I'm also initializing the OSGi console with no exit so
that I can see the OSGi status when I'm done.
The first thing the EclipseStarter does is set the PROP_INSTALL_AREA
system property ("osgi.install.area") to the directory of the system jar
(i.e. /root/plugins). This overwrites any value that the system property
already has. (The fact that this system property is essentially
read-only is not clear from the documentation.)
The configurator starts but does not find my test jar, or any jar for
that matter. Near as I can tell from my debugging, when the configurator
is going to look for plugins, it appends "/plugins" to the install area,
and thus looks in /root/plugins/plugins. This is obviously not right. To
me there appears to be an "impedance mismatch" between Eclipse and OSGi.
1) Has this been changed in 3.2?
2) Do those who use the OSGi system jar with the configurator put the
system jar in the parent directory (e.g. /root in my layout)?
3) What am I supposed to do if I want the Eclipse disk layout? Should I
start my process with startup.jar, or will I run into the same type of
problem?
Thanks in advance.
/djk
|
|
|
| Re: problem with EclipseStarter [message #57865 is a reply to message #56943] |
Tue, 24 January 2006 04:42  |
Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
This sounds like a great bug report. Certainly what you are proposing
should work. Can you try this same thing with 3.2 and report on your
success/failure?
Jeff
"David Kemper" <djk@tibco.com> wrote in message
news:dqhev3$kr$1@utils.eclipse.org...
> I'm still using the latest official 3.1.1 Eclipse release with its
> Equinox internals, and I'm having issues launching Equinox with the
> update configurator.
>
> I apologize for the length of this post. I thought it better to be as
> complete as I can. Specifically:
>
> I have the following disk layout.
>
> /root
> /plugins
> org.eclipse.osgi_3.1.1.jar
> org.eclipse.core.runtime_3.1.1.jar
> org.eclipse.update.configurator_3.1.0.jar
> my.test_1.0.0.jar
>
> In other words, I want my disk layout to mirror that of Eclipse
> including, eventually, support for /root/features.
>
> I'm invoking a JVM with a class-path of
>
> /root/plugins/org.eclipse.osgi_3.1.1.jar
>
> I'm setting the system properties: (\+line breaks for formatting)
>
> ---start properties
>
> osgi.bundles=\
> org.eclipse.core.runtime@1:start,\
> org.eclipse.update.configurator@2:start
>
> osgi.configuration.area=\
> /root/config
>
> eclipse.ignoreApp=
> true
>
> ---end properties
>
> I'm using org.eclipse.core.runtime.adaptor.EclipseStarter.main() as my
> Java entry point. I'm also initializing the OSGi console with no exit so
> that I can see the OSGi status when I'm done.
>
> The first thing the EclipseStarter does is set the PROP_INSTALL_AREA
> system property ("osgi.install.area") to the directory of the system jar
> (i.e. /root/plugins). This overwrites any value that the system property
> already has. (The fact that this system property is essentially
> read-only is not clear from the documentation.)
>
> The configurator starts but does not find my test jar, or any jar for
> that matter. Near as I can tell from my debugging, when the configurator
> is going to look for plugins, it appends "/plugins" to the install area,
> and thus looks in /root/plugins/plugins. This is obviously not right. To
> me there appears to be an "impedance mismatch" between Eclipse and OSGi.
>
> 1) Has this been changed in 3.2?
>
> 2) Do those who use the OSGi system jar with the configurator put the
> system jar in the parent directory (e.g. /root in my layout)?
>
> 3) What am I supposed to do if I want the Eclipse disk layout? Should I
> start my process with startup.jar, or will I run into the same type of
> problem?
>
> Thanks in advance.
>
> /djk
|
|
|
Powered by
FUDForum. Page generated in 0.02414 seconds
] 
Search
Help
Register
Login
Home
