I was updating the selfhosting doc and realized that one of the reasons it is complex is because the selfhosting support is not available in binary form that people can just add to their dev install. If it were then we would eliminate the need for Left (or Left would become Middle). The problem with doing this is that sometimes there are metadata changes etc that require you to update both the selfhosting code itself and the prov code you are developing (against). If we can work out the mechanics of it, it would be interesting to see if we can get the selfhosting support available in binary form...
Thoughts? Jeff Jeff McAffer/Ottawa/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/23/2007 11:56 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] provisioning self hosting Not sure I understand. If one is writing some system that calls the provisioning API, they need to selfhost. Such a person may have no interest in how provisioning works, writing tools for it, ... They simply want to call the code to have things installed at runtime. An example would be someone porting TOAST to use the new provisioning stuff. They had their own provisioning, then put it one Update Manager and now want to put it on the new provisioning system. They develop bundles that have nothing to do with provisioning but when they run they need to be able to dynamically install them without having to "deploy" or generate metadata manually or... Code and run. The proviisoning Geting Started page is targetted at people looking to get started with the provisioning code. By definition it seems then that they fall into the groups you have identified plus the folks I pointed out. Who else would be reading the getting started page? BTW, I have no problem splitting up the page but am not clear on how to do that. Jeff Pascal Rapicault/Ottawa/[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/23/2007 09:02 AM Please respond to Equinox development mailing list <equinox-dev@eclipse.org> To Equinox development mailing list <equinox-dev@eclipse.org> cc equinox-dev@eclipse.org, [EMAIL PROTECTED] Subject Re: [equinox-dev] provisioning self hosting I helped Andrew O. with the self hosting setup and what became apparent at that time was this is *not* a getting started scenario for someone just willing to step through an installation. This setup is interesting for two groups of people, the tool smiths willing to understand how provisioning and PDE will be reconciliated in 3.4, and people willing to setup complex provisioning scenario without writing metadata manually. However those expectations were not clear, and scared people away from provisioning. Rather than building up this page I would appreciate if you could split the self hosting doc into its separate page. PaScaL Jeff McAffer/Ottawa/IB [EMAIL PROTECTED] To Sent by: equinox-dev@eclipse.org equinox-dev-bounc cc [EMAIL PROTECTED] Subject [equinox-dev] provisioning self 07/22/2007 09:23 hosting PM Please respond to Equinox development mailing list <[EMAIL PROTECTED] pse.org> In looking through provisioning bug reports recently there have been a few cases where people have expressed frustration or problems with their selfhosting setup. The configuration is currently quite sensitive but does seem to work quite well if you know how to care for it. A while ago I took a stab at a selfhosting How-to on the wiki http://wiki.eclipse.org/Equinox_Provisioning_Getting_Started#Setting_up_selfhosting This is pretty bare bones and does not have some level of detail needed in real life (e.g., the metadata locations to delete in case of problems etc) Since selfhosting is so central to the development workflow, it would be great to refine the steps in the howto and hightlight the pitfalls/cures. What I propose is to work with anyone and everyone who is having selfhosting problems and then document the problems and solutions as well enhance the steps based on feedback. It might be most effective if we simply scheduled a selfhosting call and people with problems/contributions could dial in. Alternatively, we could use part of the regular provisioning call (if there are alot of people interested/having problems). Alternatively, if there are only a few people, one on one might work. Thoughts? Jeff _______________________________________________ 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