Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Spaces
Architecture
The project has been dormant for a bit, and we now start to elaborate on architecture, project plan, etc. This page should become the "spaces index page". I am adding new content as subpages under this page as a starting point.
- Spaces/Tasklist
- Spaces/Architecture
- Spaces/Naming
- Applications
- Spaces/Milestones
- Spaces/Use Cases
- Spaces/Spi/ProviderSpi - what a space provider should implement
- Spaces/Spi/PublisherSpi - extension for new ways to publish artifacts (not implemented by service provider)
- Spaces/Authorization Support - description of how to work with authorization
- Spaces/Building from source - how to build the Spaces update site
- Spaces/Standalone Xdrive - how to use the xdrive bundle stand alone (no eclipse runtime)
The Spaces project will provide an extensible framework and exemplary implementation for an Eclipse feature/plug-in set that streamlines the process of publishing, materializing and sharing a code base against a specified set of virtual services for source management, release staging and downloading, bug-tracking and community collaboration. The initial exemplary implementation will include an adapter to connect the framework to an extended version of AOL's virtual storage infrastructure (XDrive). Other exemplary implementations to capable and available virtual infrastructures will be included based on community demand and project resources (the project welcomes additional contributors to help with, e.g., an adapter to SourceForge).
Testing
Test instructions can be found here: Spaces Testing