[equinox-dev] [prov] p2 naming
Just to nip this in the bud... The proposed, voted on and approved name is "p2" not "P2". Jeff ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Compilation warnings in latest nightly build
Thanks for the info and the lead-in Olivier. As you may have noticed the new bundles contributed by Prosyst have been added to the equinox incubator build and can now be downloaded from the equinox download page. I updated the projects with the following: - added .qualifier to the Bundle-Version - added appropriate Bundle-RequiredExecutionEnvironment headers and updated compiler settings to use the proper execution environment JRE to build. - updated the settings the equinox code formatter and to format and organize imports on Java file saves - formatted and organized imports of all the code according to the new settings - fixed the compiler warnings from the build Over the next few milestones we will be reviewing the code and getting it into shape for graduation out of the incubator. Any help from the community in testing and reviewing the code is appreciated. Please use the bundles from the equinox download page and open any bugs for issues you may find. Thanks. Tom Olivier Thomann To Sent by: equinox-dev@eclipse.org equinox-dev-bounc cc [EMAIL PROTECTED] Subject [equinox-dev] Compilation warnings 09/11/2007 09:16 in latest nightly build AM Please respond to Equinox development mailing list <[EMAIL PROTECTED] pse.org> Hi, Several warnings were found in last nightly build. Here is a list of concerned bundles: - org.eclipse.equinox.ds - org.eclipse.equinox.io - org.eclipse.equinox.ip - org.eclipse.equinox.util - org.eclipse.equinox.wireadmin Please review the warnings from the nightly build results. These warnings are trivial to address. If you wonder why it is useful to provide a serialVersionUID field, I would suggest the reading of the tutorial about serialization. The projects' settings can also be modified to prevent this kind of warnings in future builds. If you don't know how to do that, let me know. Olivier ___ 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 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/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/11/2007 10:33 AM Please respond to Equinox development mailing list To Equinox development mailing list 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 <[EMAIL PROTECTED]> To: Equinox development mailing list 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 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 (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 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) (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... 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 a
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 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 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 (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 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) (Embedded image moved to file: pic08629.gif) Subject (Embedded image moved to file: pic01938.gif) [equinox-dev] Launcher and fragments
[equinox-dev] Compilation warnings in latest nightly build
Hi, Several warnings were found in last nightly build. Here is a list of concerned bundles: - org.eclipse.equinox.ds - org.eclipse.equinox.io - org.eclipse.equinox.ip - org.eclipse.equinox.util - org.eclipse.equinox.wireadmin Please review the warnings from the nightly build results. These warnings are trivial to address. If you wonder why it is useful to provide a serialVersionUID field, I would suggest the reading of the tutorial about serialization. The projects' settings can also be modified to prevent this kind of warnings in future builds. If you don't know how to do that, let me know. Olivier ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Launcher and fragments
Both the eclipse.exe and the equinox.launcher bundle may load the native library in launcher 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 Pascal Rapicault To Sent by: Equinox development mailing list equinox-dev-bounc [EMAIL PROTECTED] cc Subject 09/11/2007 08:43 [equinox-dev] Launcher and AMfragments Please respond to Equinox development mailing list <[EMAIL PROTECTED] pse.org> Hello, I'm questioning why the launcher... 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 <><><>___ 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... 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
[equinox-dev] Provisioning Symposium at Eclipse Summit Europe
First off, the Eclipse Summit Europe is coming and is looking like a great event. http://eclipsesummit.org/summiteurope2007/ Last year there were a series of very cool symposia during the conference. This year that set has been expanded and now occupy a full day prior to the main event. http://eclipsesummit.org/summiteurope2007/index.php?page=tuesday/ Tim Webb (Maya) and I are hosting a Provisioning Symposium with the intention of following on from the Ganymede Provisioning workshop held in the spring. That workshop was very successful as a context-setting and initial direction setting effort. Several key connections were made and fruit of those connections has been born. In the intervening months both the Equinox provisioning effort (now called "p2") and Maya have made progress and much code has been written. This symposium brings together committers and interested parties to report on and evaluate current provisioning initiatives, sketch efficient and practical solutions to real provisioning problems and identify opportunities for cooperation. http://eclipsesummit.org/summiteurope2007/index.php?page=detail/&id=5 The symposium is structured as a relatively informal gathering where the focus is on discussion, not presentation. To facilitate that discussion we are asking potential participants to send in a position paper describing their interests. This does not have to be anything fancy or long. Just outline what your use cases, interests, code, ... See the symposium description for more details. http://eclipsesummit.org/summiteurope2007/index.php?page=symposiaformat/ Hope to see you there. Jeff/Tim___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
