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
