[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[tycho-user] FW: Steps before deprecating eclipse-update-site
- From: "Oberlies, Tobias" <tobias.oberlies@xxxxxxx>
- Date: Thu, 14 Apr 2011 21:59:38 +0200
- Accept-language: en-US
- Acceptlanguage: en-US
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acv61xc62rTTrLtvRdCfUvGU922nDQAB1ggg
- Thread-topic: Steps before deprecating eclipse-update-site
With eclipse-repository becoming more mature and more complete, I believe it is time to get rid of the duplication of packaging types for building p2 repositories in Tycho. As a first step, we should mark eclipse-update-site as deprecated, once eclipse-repository can be used in all supported cases.
I currently only know case where using eclipse-repository is not yet possible: if the target platform is defined via pomDependencies=consider . This issue should be resolved soon; we are planning to work on this from next week. After this we will replace eclipse-update-site by eclipse-repository in the Tycho integration tests - to be sure that everything is covered.
Do you know of additional cases where eclipse-repository is lacking functionality or is not suited for your needs? If yes, please create bugs or enhancement requests and link them to the umbrella bug for the eclipse-update-site deprecation . If you have more general concerns, we can also discuss them here.
 https://issues.sonatype.org/browse/TYCHO-570 : Artifacts from POM dependencies missing in eclipse-repository
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=342876 : Deprecate packaging type eclipse-update-site