https://github.com/ivandavidov/eclipse-equinox-osgi-p2-tutorial
Eclipse Equinox OSGi p2 tutorial with samples for the publisher and the director applications.
https://github.com/ivandavidov/eclipse-equinox-osgi-p2-tutorial
eclipse equinox osgi p2 tutorial
Last synced: 7 months ago
JSON representation
Eclipse Equinox OSGi p2 tutorial with samples for the publisher and the director applications.
- Host: GitHub
- URL: https://github.com/ivandavidov/eclipse-equinox-osgi-p2-tutorial
- Owner: ivandavidov
- License: gpl-3.0
- Created: 2016-01-22T23:14:52.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2017-05-18T17:57:39.000Z (over 8 years ago)
- Last Synced: 2025-01-17T18:22:36.561Z (9 months ago)
- Topics: eclipse, equinox, osgi, p2, tutorial
- Language: Batchfile
- Homepage:
- Size: 21.5 KB
- Stars: 7
- Watchers: 3
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Eclipse-Equinox-OSGi-p2-Tutorial
## About
This project includes Eclipse Equinox OSGi specific samples which cover the following scenarios:
* Publisher scenario: Create a simple p2 repository which contains only one bundle. This is the Equniox launcher bundle. This invokes the Publisher (org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher) application. The Publisher application creates p2 metadata for the repository containing the single bundle. Check the created `test_repo` folder.
* Director scenario: Create a p2 profile which contains metadata for the bundle from the previously created repository. This involves the Director (org.eclipse.equinox.p2.director) application. Check the created `test_profile` foldr. TODO more explanations.
* Console scenario: Start an Equinox OSGi console.
These scenarios run only on Windows as `.cmd` scripts are provided.
TODO - add explanations about the agent and the connection between the downloaded equinox repository, the agent and the applications.
## Getting started
Start with the `README.txt` inside the `equinox_repo` folder.
Then run the command-line scripts.
## LICENSE
Check out the license text inside the `LICENSE` file.