[equinox-dev] Launcher for Equinox
Hi, I am sorry if this is not the right place for this post, but I would appreciate the opinion and answers from people who know more about Equinox and different ways to launch it. What is it the most common way to launch Equinox without using Eclipse? I have the next problem, I would like to have system bundles which are installed from the beggining, one of this bundles has the InstallerBundle role, so it is used in order to install another bundles by programming. Since I would like to achieve a fast deployment I start to use Pax Runner but I had to change this launcher because the persistence did not work fine here. I mean, if I installed a bundle in run time by using Pax Runner context I have not found way to achieve persistence in the bundles which were installed in run time. The bundles' states were not kept once I restarted Pax Runner. On the other hand, I have tried by using config.ini file as it is said in [1]. But the problem here is that if I launch the command [2] to load config.ini from CONFIG_INI_FOLDER the first time Equinox installs and starts the written bundles in config.ini in a right way. But if I want to launch Equinox by keeping the bundles' state in the second launching by removing -configuration CONFIG_INI_FOLDER I just get the framework Equinox bundle installed instead of the other bundles from config.ini file. How can I install a set of bundles automatically and then launch Equinox framework in order to keep the bundles' states for the next running? I would like on the one hand to have a simple and fast way to install and start a set of system bundles without to install one to one each bundle. On the other hand I would like to use this installation context to launch Equinox in normal way, I mean, where I could use the different capabilities that OSGi specification provides, keeping the bundles's state, keeping as installed bundles those bundles which were installed programmatically, and so on. How do you achieve this? [1] http://www.eclipse.org/equinox/documents/quickstart.php [2] java -jar org.eclipse.osgi_3.5.jar -console -configuration CONFIG_INI_FOLDER Any idea will appreciated. Thank you in advance David ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
RE: [equinox-dev] Launcher for Equinox
Hi Ali, Thank you very much for your answer. I have tried by launching with -configuration command and then I stopped one of the bundles which appear in config.ini, let's call it bundle A, so,launching again the command without removing -configuration command the state of the bundle A it is STARTED and not STOPPED as I left it the last time. By the way, I have tried to install a new bundle by command (install file:bundle_location.jar) in running time and this bundle keeps installed the next time I launch the framework, so this is something that I needed which it is working fine. So now I just need that bundles, which were installed by using config.ini file, keep their status each time I restart the framework. How could I achieve this? I will check the Equinox's Launcher Thanks Regards David De: Ali Naddaf [mailto:ali.nad...@gmail.com] Enviado el: lunes, 15 de marzo de 2010 17:28 Para: Equinox development mailing list CC: David Conde Asunto: Re: [equinox-dev] Launcher for Equinox David, Regarding the part that you are using the config.ini, why do you remove that command line option on the subsequent launches? If you keep it there, then it will reuse the cache that it was built the last time under that configuration folder and you should achieve what you want; I am guessing that your config folder is different from config, underneath where you run your command line, so the next time, after removing that command line option, it looks into the ./config/ directory and doesn't see anything there so it only starts the framework with no additional bundles. You can also use launchers that are built as part of the equinox [1] if the binary for your hardware is available. Ali. [1] http://wiki.eclipse.org/index.php/Equinox_Launcher (I don't know how up-to-date this is but is a good starting point) On 3/15/2010 11:24 AM, David Conde wrote: Hi, I am sorry if this is not the right place for this post, but I would appreciate the opinion and answers from people who know more about Equinox and different ways to launch it. What is it the most common way to launch Equinox without using Eclipse? I have the next problem, I would like to have system bundles which are installed from the beggining, one of this bundles has the InstallerBundle role, so it is used in order to install another bundles by programming. Since I would like to achieve a fast deployment I start to use Pax Runner but I had to change this launcher because the persistence did not work fine here. I mean, if I installed a bundle in run time by using Pax Runner context I have not found way to achieve persistence in the bundles which were installed in run time. The bundles' states were not kept once I restarted Pax Runner. On the other hand, I have tried by using config.ini file as it is said in [1]. But the problem here is that if I launch the command [2] to load config.ini from CONFIG_INI_FOLDER the first time Equinox installs and starts the written bundles in config.ini in a right way. But if I want to launch Equinox by keeping the bundles' state in the second launching by removing -configuration CONFIG_INI_FOLDER I just get the framework Equinox bundle installed instead of the other bundles from config.ini file. How can I install a set of bundles automatically and then launch Equinox framework in order to keep the bundles' states for the next running? I would like on the one hand to have a simple and fast way to install and start a set of system bundles without to install one to one each bundle. On the other hand I would like to use this installation context to launch Equinox in normal way, I mean, where I could use the different capabilities that OSGi specification provides, keeping the bundles's state, keeping as installed bundles those bundles which were installed programmatically, and so on. How do you achieve this? [1] http://www.eclipse.org/equinox/documents/quickstart.php [2] java -jar org.eclipse.osgi_3.5.jar -console -configuration CONFIG_INI_FOLDER Any idea will appreciated. Thank you in advance David ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [launcher] Showsplash
I am using a freeware tool (http://www.angusj.com/resourcehacker/) to modify our win32 NL for smartup so that is possible to change (branding) the splash screen and string resources without the need of recompiling our NL. However, this is not done at install time, although it might be possible, because this tool can run in command line mode. Just another thought. Jeff McAffer wrote: alternatively is it possible to have the installer configure the launcher with the right splash? of course that assumes that the NL is fixed from install time. Just a thought Jeff Andrew Niefer wrote: James, The native code that is showing the early splash screen does not have support to change the bitmap that is being shown. This means that you need to wait until swt is available before it can be refreshed. With SWT I believe changing the image is just setting the BackgroundImage on the shell. The simplest way of contributing SWT to the splash screen is to use the workbench org.eclipse.ui.splashHandlers extension point and extend the EclipseSplashHandler class. The only problem is that the code that handles the osgi.splashPath and searches for NL variants (Main.getSplashLocation Main.searchForSplash) is not available available outside of Main. You will probably have to do that search yourself. -Andrew *James D Miles [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 02/06/2008 11:01 AM Please respond to Equinox development mailing list equinox-dev@eclipse.org To equinox-dev@eclipse.org cc Subject [equinox-dev] [launcher] By using the -showsplash I can get an early splash screen. However when not using this mechanism we were able to set osgi.splashPath with a comma separated list of URLs. We still need the splash selection based on nl that we got when using osgi.splashPath. How can we get the splashpath bmp refreshed after early startup? The default behavior seems to be to continue using the early splash screen.___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [launcher] Showsplash
Yes we could do something like that but we need it to change it based on nl. We currently have about 600K bmp for each language specific splash screen that we provide. So what would be better is if we could write the actual text in the SWTsplash window with the progress monitor. Then we would only need one bmp. Jeff McAffer [EMAIL PROTECTED] Sent by: To equinox-dev-bounc Equinox development mailing list [EMAIL PROTECTED]equinox-dev@eclipse.org cc 02/07/2008 07:50 Subject AMRe: [equinox-dev] [launcher] Showsplash Please respond to Equinox development mailing list [EMAIL PROTECTED] pse.org alternatively is it possible to have the installer configure the launcher with the right splash? of course that assumes that the NL is fixed from install time. Just a thought Jeff Andrew Niefer wrote: James, The native code that is showing the early splash screen does not have support to change the bitmap that is being shown. This means that you need to wait until swt is available before it can be refreshed. With SWT I believe changing the image is just setting the BackgroundImage on the shell. The simplest way of contributing SWT to the splash screen is to use the workbench org.eclipse.ui.splashHandlers extension point and extend the EclipseSplashHandler class. The only problem is that the code that handles the osgi.splashPath and searches for NL variants (Main.getSplashLocation Main.searchForSplash) is not available available outside of Main. You will probably have to do that search yourself. -Andrew *James D Miles [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 02/06/2008 11:01 AM Please respond to Equinox development mailing list equinox-dev@eclipse.org To equinox-dev@eclipse.org cc Subject [equinox-dev] [launcher] By using the -showsplash I can get an early splash screen. However when not using this mechanism we were able to set osgi.splashPath with a comma separated list of URLs. We still need the splash selection based on nl that we got when using osgi.splashPath. How can we get the splashpath bmp refreshed after early startup? The default behavior seems to be to continue using the early splash screen.___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: pic26828.gifinline: ecblank.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [launcher] Showsplash
In the case of the splash screen, it is a simple line in the eclipse.ini file which indicates the splash bitmap to use. The difference between an english and a german splash screen could be as simple as -showsplash org.foo.branding/en/splash.bmp -showsplash org.foo.branding/de/splash.bmp I expect that since the launcher fragments can contribute --launcher.library lines to the .ini file, it should be possible for branding IUs to contribute -showsplash. Though I'm not sure if a single IU can contribute different arguments depending on a platform/nl filter, it might require branding fragments? -Andrew Stefan Liebig [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 02/07/2008 09:44 AM Please respond to Equinox development mailing list equinox-dev@eclipse.org To Equinox development mailing list equinox-dev@eclipse.org cc Subject Re: [equinox-dev] [launcher] Showsplash I am using a freeware tool (http://www.angusj.com/resourcehacker/) to modify our win32 NL for smartup so that is possible to change (branding) the splash screen and string resources without the need of recompiling our NL. However, this is not done at install time, although it might be possible, because this tool can run in command line mode. Just another thought. Jeff McAffer wrote: alternatively is it possible to have the installer configure the launcher with the right splash? of course that assumes that the NL is fixed from install time. Just a thought Jeff Andrew Niefer wrote: James, The native code that is showing the early splash screen does not have support to change the bitmap that is being shown. This means that you need to wait until swt is available before it can be refreshed. With SWT I believe changing the image is just setting the BackgroundImage on the shell. The simplest way of contributing SWT to the splash screen is to use the workbench org.eclipse.ui.splashHandlers extension point and extend the EclipseSplashHandler class. The only problem is that the code that handles the osgi.splashPath and searches for NL variants (Main.getSplashLocation Main.searchForSplash) is not available available outside of Main. You will probably have to do that search yourself. -Andrew *James D Miles [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 02/06/2008 11:01 AM Please respond to Equinox development mailing list equinox-dev@eclipse.org To equinox-dev@eclipse.org cc Subject [equinox-dev] [launcher] By using the -showsplash I can get an early splash screen. However when not using this mechanism we were able to set osgi.splashPath with a comma separated list of URLs. We still need the splash selection based on nl that we got when using osgi.splashPath. How can we get the splashpath bmp refreshed after early startup? The default behavior seems to be to continue using the early splash screen.___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [launcher] Showsplash
alternatively is it possible to have the installer configure the launcher with the right splash? of course that assumes that the NL is fixed from install time. Just a thought Jeff Andrew Niefer wrote: James, The native code that is showing the early splash screen does not have support to change the bitmap that is being shown. This means that you need to wait until swt is available before it can be refreshed. With SWT I believe changing the image is just setting the BackgroundImage on the shell. The simplest way of contributing SWT to the splash screen is to use the workbench org.eclipse.ui.splashHandlers extension point and extend the EclipseSplashHandler class. The only problem is that the code that handles the osgi.splashPath and searches for NL variants (Main.getSplashLocation Main.searchForSplash) is not available available outside of Main. You will probably have to do that search yourself. -Andrew *James D Miles [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 02/06/2008 11:01 AM Please respond to Equinox development mailing list equinox-dev@eclipse.org To equinox-dev@eclipse.org cc Subject [equinox-dev] [launcher] By using the -showsplash I can get an early splash screen. However when not using this mechanism we were able to set osgi.splashPath with a comma separated list of URLs. We still need the splash selection based on nl that we got when using osgi.splashPath. How can we get the splashpath bmp refreshed after early startup? The default behavior seems to be to continue using the early splash screen.___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [launcher] Showsplash
Sure then you can do it the way that Andrew suggested. Essentially come up with a non-localised splash and write in localized info when SWT is up. Or you can tell the launcher to not show the splash and put it up the old way after some delay while Java starts. Jeff James D Miles wrote: Yes we could do something like that but we need it to change it based on nl. We currently have about 600K bmp for each language specific splash screen that we provide. So what would be better is if we could write the actual text in the SWTsplash window with the progress monitor. Then we would only need one bmp. Inactive hide details for Jeff McAffer [EMAIL PROTECTED]Jeff McAffer [EMAIL PROTECTED] *Jeff McAffer [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 02/07/2008 07:50 AM Please respond to Equinox development mailing list equinox-dev@eclipse.org To Equinox development mailing list equinox-dev@eclipse.org cc Subject Re: [equinox-dev] [launcher] Showsplash alternatively is it possible to have the installer configure the launcher with the right splash? of course that assumes that the NL is fixed from install time. Just a thought Jeff Andrew Niefer wrote: James, The native code that is showing the early splash screen does not have support to change the bitmap that is being shown. This means that you need to wait until swt is available before it can be refreshed. With SWT I believe changing the image is just setting the BackgroundImage on the shell. The simplest way of contributing SWT to the splash screen is to use the workbench org.eclipse.ui.splashHandlers extension point and extend the EclipseSplashHandler class. The only problem is that the code that handles the osgi.splashPath and searches for NL variants (Main.getSplashLocation Main.searchForSplash) is not available available outside of Main. You will probably have to do that search yourself. -Andrew *James D Miles [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 02/06/2008 11:01 AM Please respond to Equinox development mailing list equinox-dev@eclipse.org To equinox-dev@eclipse.org cc Subject [equinox-dev] [launcher] By using the -showsplash I can get an early splash screen. However when not using this mechanism we were able to set osgi.splashPath with a comma separated list of URLs. We still need the splash selection based on nl that we got when using osgi.splashPath. How can we get the splashpath bmp refreshed after early startup? The default behavior seems to be to continue using the early splash screen.___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] [launcher]
By using the -showsplash I can get an early splash screen. However when not using this mechanism we were able to set osgi.splashPath with a comma separated list of URLs. We still need the splash selection based on nl that we got when using osgi.splashPath. How can we get the splashpath bmp refreshed after early startup? The default behavior seems to be to continue using the early splash screen.___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [launcher] Showsplash
James, The native code that is showing the early splash screen does not have support to change the bitmap that is being shown. This means that you need to wait until swt is available before it can be refreshed. With SWT I believe changing the image is just setting the BackgroundImage on the shell. The simplest way of contributing SWT to the splash screen is to use the workbench org.eclipse.ui.splashHandlers extension point and extend the EclipseSplashHandler class. The only problem is that the code that handles the osgi.splashPath and searches for NL variants (Main.getSplashLocation Main.searchForSplash) is not available available outside of Main. You will probably have to do that search yourself. -Andrew James D Miles [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 02/06/2008 11:01 AM Please respond to Equinox development mailing list equinox-dev@eclipse.org To equinox-dev@eclipse.org cc Subject [equinox-dev] [launcher] By using the -showsplash I can get an early splash screen. However when not using this mechanism we were able to set osgi.splashPath with a comma separated list of URLs. We still need the splash selection based on nl that we got when using osgi.splashPath. How can we get the splashpath bmp refreshed after early startup? The default behavior seems to be to continue using the early splash screen. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev]Launcher projects tagged for 6pm build
The map file has been updated for the following Bug changes: + Bug 199020. [launcher] Can't start the AWT while using new eclipse native launcher in 3.3 (NEW) The following projects have changed: org.eclipse.equinox.launcher.carbon.macosx org.eclipse.equinox.executable___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Launcher and fragments
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
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 [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-bouTo [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
