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.
Difference between revisions of "Equinox/p2/Hosting repositories"
(New page: Hosting a p2 repository on a web server does not require any specific capabilities from the server: no servlet, no PHP, nothing. Just the ability to server files.) |
|||
| Line 1: | Line 1: | ||
| − | Hosting a p2 repository on a web server does not require any specific capabilities from the server: no servlet, no PHP, nothing. Just the ability to server files. | + | Hosting a p2 repository on a web server does not require any specific capabilities from the server: no servlet, no PHP, nothing. Just the ability to serve files,. |
| + | |||
| + | In order to make a repository available on a server, simply copy the files produced by the export/build of the feature or the product on the server. | ||
| + | Typically a repository looks like this, but there could also be other files. | ||
| + | |||
| + | content.xml (or content.jar) | ||
| + | artifacts.xml (or artifacts.jar) | ||
| + | plugins/ | ||
| + | <files> | ||
| + | features/ | ||
| + | <files> | ||
| + | binary/ | ||
| + | <files> | ||
| + | |||
| + | Producers of repositories may be interested in reading the recommendations on [[Repository_retention_policy|repository retention policies]]. | ||
| + | |||
| + | [[Category:Equinox_p2]] | ||
Revision as of 20:11, 2 November 2009
Hosting a p2 repository on a web server does not require any specific capabilities from the server: no servlet, no PHP, nothing. Just the ability to serve files,.
In order to make a repository available on a server, simply copy the files produced by the export/build of the feature or the product on the server. Typically a repository looks like this, but there could also be other files.
content.xml (or content.jar)
artifacts.xml (or artifacts.jar)
plugins/
<files>
features/
<files>
binary/
<files>
Producers of repositories may be interested in reading the recommendations on repository retention policies.