Community
Participate
Working Groups
We are still autogenerating projects for org.eclipse.orion.client.core and org.eclipse.orion.client.editor. If anything, we should be autogenerating clones to the orion repos. Perhaps we should revisit this when we add the landing page.
It is handy for people kicking the tires, but I would vote to remove it after M7. Because it is a shared project it is a bit goofy appearing on orionhub.org for example. People have made all kinds of modifications to those shared files so now it is just garbage. The original motivation is that it was hard to get started to try Orion out. Now, you can import a zip, via SFTP, and via cloning a Git repository. If there was some kind of landing page that guided users towards these options it would eliminate the need for them entirely. I will take the work item to remove this code, but others please chime in with your thoughts.
+1 to remove. It's particularly confusing for self-hosters or cloners, because if you don't immediately remove it from your workspace, you can confuse it with your "real" folders of the same names.
I have removed the code that creates those projects automatically, but I believe there is something Andrew needs to do on the build side to avoid adding that content into the serverworkspace.
My server change is here: http://git.eclipse.org/c/e4/org.eclipse.orion.server.git/commit/?id=66b061c9c4cdd885a340b696db6535f86fe57dd3
I have removed the code that copies the projects into the final archives. The eclipse.ini still contains a "-data serverworkspace" which will now be create as an empty workspace on startup.
