[equinox-dev] [prov] Shared install
Tim, Andrew, For records, could you guys write a short wiki describing the various approaches we talked about to implement shared installs? In a few months this will help us remember why/or not we've done what we've done :-) Also , following the call, Simon and I had further discussions and believe a good approach would be: - simple configurator reads the user bundles.txt - simple configurator reads the shared bundles txt - if the shared bundles.txt has changed, only run with its content (ignore bundles from the user), since it should be a consistent whole (composed of the agent / reconciler) - then run the reconciler on the running profile (we may need another operation on the director or something like that). Note here I'm not saying when it is actually run and this should just be configurable. Something like that offers the advantage that - we don't need to have another configurator as we had touched on previously - we should always be able to start something - gives flexibility as to when the reconciliation should be done HTH, PaScaL ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Equinox coding conventions
I updated the following equinox projects to have the latest Equinox code convention settings. I also updated each project to format java files when saving. You may notice additional changes when saving java files and creating patches. In this case the code was probably not correctly formatted. org.eclipse.equinox.app org.eclipse.equinox.common org.eclipse.equinox.device org.eclipse.equinox.event org.eclipse.equinox.http org.eclipse.equinox.http.jetty org.eclipse.equinox.http.registry org.eclipse.equinox.http.servlet org.eclipse.equinox.http.servletbridge org.eclipse.equinox.jsp.jasper org.eclipse.equinox.jsp.jasper.registry org.eclipse.equinox.launcher org.eclipse.equinox.log org.eclipse.equinox.metatype org.eclipse.equinox.preferences org.eclipse.equinox.registry org.eclipse.equinox.servletbridge org.eclipse.equinox.supplement org.eclipse.equinox.useradmin org.eclipse.osgi Because of bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=200207 the org.eclipse.osgi project cannot set the Malformed Javadoc compiler settings to Error. All other projects do have this set to Error. Tom John Arthorne [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 08/20/2007 04:35 PM Please respond to Equinox development mailing list equinox-dev@eclipse.org To equinox-dev@eclipse.org cc Subject [equinox-dev] Equinox coding conventions As more and more people are contributing to Equinox (Thanks!) we thought it would make sense to point out the Equinox coding conventions: http://www.eclipse.org/equinox/documents/coding.php In some ways these sort of guidelines can show up as restricting one's freedom of artistic code formatting or variable naming expression. In practice however, having a common set of coding practices is one of the ingredients of our success. We have a large and growing body of committers in Equinox, and a much larger community looking in and trying to understand what we write. Having common and consistent conventions makes our code easier to read and work with for everyone. In particular, check out the section around formatter and compiler settings. These we should setup in each project so that everyone is seeing the same errors and formatting the same way. We're also going to experiment with enabling automatic formatting and code cleanup on save, so we can just forget about these issues and let the tools do the work. ___ 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] Equinox coding conventions
Great! Thanks Tom. Can someone do this for the provisioning projects as well? Some of them have the some of the right settings but it would be good to have a complete pass over them to ensure consistency etc. Jeff Thomas Watson [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 08/21/2007 12:55 PM 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] Equinox coding conventions I updated the following equinox projects to have the latest Equinox code convention settings. I also updated each project to format java files when saving. You may notice additional changes when saving java files and creating patches. In this case the code was probably not correctly formatted. org.eclipse.equinox.app org.eclipse.equinox.common org.eclipse.equinox.device org.eclipse.equinox.event org.eclipse.equinox.http org.eclipse.equinox.http.jetty org.eclipse.equinox.http.registry org.eclipse.equinox.http.servlet org.eclipse.equinox.http.servletbridge org.eclipse.equinox.jsp.jasper org.eclipse.equinox.jsp.jasper.registry org.eclipse.equinox.launcher org.eclipse.equinox.log org.eclipse.equinox.metatype org.eclipse.equinox.preferences org.eclipse.equinox.registry org.eclipse.equinox.servletbridge org.eclipse.equinox.supplement org.eclipse.equinox.useradmin org.eclipse.osgi Because of bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=200207 the org.eclipse.osgi project cannot set the Malformed Javadoc compiler settings to Error. All other projects do have this set to Error. Tom John Arthorne [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 08/20/2007 04:35 PM Please respond to Equinox development mailing list equinox-dev@eclipse.org To equinox-dev@eclipse.org cc Subject [equinox-dev] Equinox coding conventions As more and more people are contributing to Equinox (Thanks!) we thought it would make sense to point out the Equinox coding conventions: http://www.eclipse.org/equinox/documents/coding.php In some ways these sort of guidelines can show up as restricting one's freedom of artistic code formatting or variable naming expression. In practice however, having a common set of coding practices is one of the ingredients of our success. We have a large and growing body of committers in Equinox, and a much larger community looking in and trying to understand what we write. Having common and consistent conventions makes our code easier to read and work with for everyone. In particular, check out the section around formatter and compiler settings. These we should setup in each project so that everyone is seeing the same errors and formatting the same way. We're also going to experiment with enabling automatic formatting and code cleanup on save, so we can just forget about these issues and let the tools do the work. ___ 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