[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [equinox-dev] Launcher and fragments
|
One reason for having the libraries
in the fragments is probably just because we couldn't think of a better
place to put them. :)
Both the exe and the launcher.jar have
a similar kind of relationship to the fragments, however, for the launcher.jar
this is an optional dependency.
We just never had a mechanism for describing
this relationship from the exe.
Note that there may be a use case to
provision the launcher.jar + fragment but not the exe.
-Andrew
Pascal Rapicault/Ottawa/IBM@IBMCA
Sent by: equinox-dev-bounces@xxxxxxxxxxx
09/11/2007 10:33 AM
|
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
|
|
To
| Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [equinox-dev] Launcher and fragments |
|
I was not suggesting the creation of an exe bundle
to be shipped with the
eclipse SDK. Instead I was trying to define what, in the absolute, these
platform specific bits were really complementary of, and I think they are
really complement of the exe since without these libraries the exe simply
does not work (Somewhat the relationship between the exe and the platform
specific launchers is the same than the relationship between swt and its
fragments). Also, they happen to be used by the launcher.jar in some
particular scenarios, but I would rather see this as an optional dependency
from the launcher.jar onto these platform specific extensions to the exe.
Of course this does not necessarily make sense from an osgi point of view.
However if you put a provisioning hat on, it changes a lot of things, since
you can reason about the dependencies between the exe and the platform
specific launchers in one abstraction. Therefore we would have an
InstallableUnit representing the eclipse.exe. This IU would eagerly require
a "platform specifc launcher" capability that would be provided
by the
InstallableUnit representing the platform specific launchers. This way
we
are sure that provisioning the eclipse.exe always causes the provisioning
of a fully functional exe. Then the launcher.jar IU would optionally
require a capability provided by the platform specific IUs.
PaScaL
From: Thomas Watson <tjwatson@xxxxxxxxxx>
To: Equinox development mailing list
<equinox-dev@xxxxxxxxxxx>
Date: 09/11/2007 10:04 AM
Subject: Re: [equinox-dev] Launcher and fragments
Both the eclipse.exe and the equinox.launcher bundle may load the native
library in launcher.<os>.<ws>.<arch>. For example when
launching
self-hosting, the eclipse.exe is not used. In this case the
equinox.launcher java code loads the shared library. Currently there is
no
eclipse.exe bundle, that left us with the equinox.launcher bundle for the
host of the shared library fragments. We could create an equinox.executable
host bundle but I'm not sure what the motivation would be for that since
it
would be an empty host that does nothing other than allow the native code
fragment bundles to resolve.
Tom
(Embedded image moved to file: pic28687.gif)Inactive hide details for
Pascal Rapicault ---09/11/2007 08:47:29 AM---Hello,Pascal Rapicault ---09
/11/2007 08:47:29 AM---Hello,
Pascal
Rapicault
<Pascal_Rapicau
lt@xxxxxxxxxx> (Embedded image moved to file:
Sent by: pic07796.gif)
equinox-dev-bou
To
nces@xxxxxxxxxx (Embedded image
moved to
g
file: pic02767.gif)
Equinox development
mailing list
09/11/2007 <equinox-dev@xxxxxxxxxxx>
08:43 AM (Embedded image moved
to file:
pic10822.gif)
cc
Please respond to
(Embedded image
moved to
Equinox development mailing list
file: pic14897.gif)
<equinox-dev@xxxxxxxxxxx>
(Embedded image moved to file:
pic08629.gif)
Subject
(Embedded image moved to
file: pic01938.gif)
[equinox-dev] Launcher
and fragments
(Embedded
image moved to file:
pic20060.gif)
(Embedded image moved to
file: pic06956.gif)
Hello,
I'm questioning why the launcher.<os>.<ws>.<arch> bundles
are fragments of
the launcher bundle?
If I remember correctly the launcher fragments result from the
reorganization of the eclipse.exe where we tried to make the exe as small
as possible. Therefore it seems to me that the declaration of the platform
specific launcher bundles as fragment of the launcher.jar (formerly
startup.jar) is abusive. However I found weird that we did without a
precise motive. Does anyone remember it?
For me, the platform specific launchers should be "fragment to the
eclipse.exe".
PaScaL
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
(See attached file: pic26003.gif)
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
Attachment:
pic28687.gif
Description: GIF image
Attachment:
pic07796.gif
Description: GIF image
Attachment:
pic02767.gif
Description: GIF image
Attachment:
pic10822.gif
Description: GIF image
Attachment:
pic14897.gif
Description: GIF image
Attachment:
pic08629.gif
Description: GIF image
Attachment:
pic01938.gif
Description: GIF image
Attachment:
pic20060.gif
Description: GIF image
Attachment:
pic06956.gif
Description: GIF image
Attachment:
pic26003.gif
Description: GIF image
