Details
-
Type:
Sub-task
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0.0-M9 (2.0.0.v20150606-M9)
-
Component/s: None
-
Labels:None
Description
Generate P2 repository / update site.
Should it be self-hosted (i.e. contain all Eclipse and 3rd party dependencies) or only contain the Studio artifacts? Need to check technical and legal details.
Check if update site works with Studio 2.0.0-M8 (RCP app or installed within Eclipse).
We should consider to use a composite repository? It allows better structure of actual Studio repository and dependencies, allows links to older versions.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
I suggest the following update site structure:
1. Three P2 repositories
1.1. dependencies
- contains the dependencies not yet available in any P2 repository: apacheds, api, mavibot, jdbm
1.2. eclipse
- contains the main features and plugins (ldapbrowser, ldifeditor, schemaeditor, apacheds, later openldap)
1.3. product
- contains the 'product' specific stuff: RCP feature and plugin, NLS feature
- probably not included in 2.0.0-M9 because right configuration it tricky
2. Two composite repositories (see https://wiki.eclipse.org/Equinox/p2/Composite_Repositories_%28new%29)
2.1. http://directory.apache.org/studio/update
- update site for installation into regular Eclipse
- includes child repositories "dependencies" and "eclipse"
- excluding 'product' and thus the RCP app because that must not be installed into a regular Eclipse
2.2. http://directory.apache.org/studio/update/product
- configured within the Studio RCP product
- includes child repositories "dependencies", "eclipse", "product" and more on demand (e.g. Eclipse Mars update site)
Done, except P2 repository for product which will be addressed in DIRSTUDIO-1053.
Update from an existing Studio 2.0.0-M8 RCP application doesn't work.
Update when plugins are installed in an Eclipse works well.