Community
Participate
Working Groups
With eclipse-repository becoming mature and more complete, we should deprecate (and eventually delete) the packaging type eclipse-update-site. This umbrella bug should collect issues that need to be resolved before we can promote eclipse-repository as the only packaging type in Tycho to build p2 repositories. With/before the deprecation, we'll also need to migrate all integration test which use eclipse-update-site to eclipse-repository. While doing this, we should create a detailed migration guide, which includes for example all configuration parameters.
There are 15 integration tests using eclipse-update-site. Migrating these and deprecating eclipse-update-site should be doable for 0.13.0.
move all bugs to post 0.14.0
I have no plans for the near future to work on this. Handing back to inbox.
The "eclipse-application" and "eclipse-update-site" packaging types have been marked as deprecated for nearly 10 years now on this wiki page: https://wiki.eclipse.org/Tycho/Packaging_Types#eclipse-repository With tycho turning moving to version 2.0, is it time to remove these packaging types?
+1 to remove anything deprecated now. @Matt: feel free to send a patch about it whenever you can.
New Gerrit change created: https://git.eclipse.org/r/164925
Gerrit change https://git.eclipse.org/r/164925 was merged to [master]. Commit: http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/commit/?id=2ecd6124f54287937e7533c3dc921eab63e5689c
New Gerrit change created: https://git.eclipse.org/r/165229
Gerrit change https://git.eclipse.org/r/c/tycho/org.eclipse.tycho/+/172149 was merged to [master]. Commit: http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/commit/?id=d154f553afbec411c5157207123315d75eab4b92
Eclipse Tycho is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/tycho/issues/ instead. If this issue is relevant to you, your action is required. 0. Verify this issue is still happening with latest Tycho 2.4.0-SNAPSHOT if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done if issue is still present when latest release: * Create a new issue at https://github.com/eclipse/tycho/issues/ ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience) ** In the GitHub description, start with a link to this bugzilla ticket ** Optionally add new content to the description if it can helps towards resolution ** Submit GitHub issue * Update bugzilla ticket ** Add to "See also" property (up right column) the link to the newly created GitHub issue ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>" ** Set status as CLOSED MOVED ** Submit All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for Tycho will be archived and made read-only.
Migrated to https://github.com/eclipse/tycho/issues/474
