Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Slingshot
Contents
An Über Repository for Eclipse Projects
What is it?
- An aggregate repository
- Like the simultaneous release repository
- But without the rigours (or quality assurances)
- A means for projects to extend their reach
- Manifests as a p2 and Maven repository
- Target Audience
- Developers/Committers
- Adopters
- Not intended to be included in packages
- Not for end-users
Opt in
To participate in Slingshot, a project must provide a " contribution" file (which uses the same format as the release train). This file is typically stored in the project's website CVS. A pointer to this file is provided via the portal using the Project's "slingshotconfigurationurl" attribute (this is a single absolute URL).
Repository
- Links to simultaneous release repository
- Retains all artifacts
- Restricted to milestones and release builds only
- Facilitates reproduceable builds
- Categorizes based on project structure
- Automated
- We don't chase down your dependencies
- That's your job!
Benefits
- Easier for developers to get the project bits
- Avenue for projects to gain exposure
- Not indended for end users
- No quality assurances