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 <[EMAIL PROTECTED]> To: Equinox development mailing list <equinox-dev@eclipse.org> 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 [EMAIL PROTECTED]> (Embedded image moved to file: Sent by: pic07796.gif) equinox-dev-bou To [EMAIL PROTECTED] (Embedded image moved to g file: pic02767.gif) Equinox development mailing list 09/11/2007 <equinox-dev@eclipse.org> 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@eclipse.org> (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@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev (See attached file: pic26003.gif) _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<attachment: pic28687.gif>>
<<attachment: pic07796.gif>>
<<attachment: pic02767.gif>>
<<attachment: pic10822.gif>>
<<attachment: pic14897.gif>>
<<attachment: pic08629.gif>>
<<attachment: pic01938.gif>>
<<attachment: pic20060.gif>>
<<attachment: pic06956.gif>>
<<attachment: pic26003.gif>>
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev