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.
Difference between revisions of "Slingshot"
(→Aggregator) |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
More discussion in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=297533 Bug 297533]. | More discussion in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=297533 Bug 297533]. | ||
| Line 20: | Line 18: | ||
Slingshot is a p2 repository aggregator. It gathers the contributions from multiple project repositories, and combines them into a single repository that is accessible as both a p2 and Maven repository. Only code that has resolvable dependencies is included in the aggregate repository. Unresolved dependencies are reported back to the project. | Slingshot is a p2 repository aggregator. It gathers the contributions from multiple project repositories, and combines them into a single repository that is accessible as both a p2 and Maven repository. Only code that has resolvable dependencies is included in the aggregate repository. Unresolved dependencies are reported back to the project. | ||
| − | + | * Includes only integration and release builds | |
| − | + | * Copies artefacts into a copy repository; | |
| − | + | * Retains all artefacts | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
==Opt in== | ==Opt in== | ||
Revision as of 15:32, 14 April 2010
More discussion in Bug 297533.
What is it?
Slingshot is an Über Repository for Eclipse Projects
- 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
Aggregator
Slingshot is a p2 repository aggregator. It gathers the contributions from multiple project repositories, and combines them into a single repository that is accessible as both a p2 and Maven repository. Only code that has resolvable dependencies is included in the aggregate repository. Unresolved dependencies are reported back to the project.
- Includes only integration and release builds
- Copies artefacts into a copy repository;
- Retains all artefacts
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