Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 565400

Summary: Remove system capabilities from Java 9+ profiles (read dynamically)
Product: z_Archived Reporter: Mickael Istria <mistria>
Component: TychoAssignee: Project Inbox <tycho-inbox>
Status: CLOSED MOVED QA Contact:
Severity: enhancement    
Priority: P3 CC: akurtakov, laeubi
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Mickael Istria CLA 2020-07-21 12:21:30 EDT
Similarly to how Tycho now reads the system packages from the installation directly with a "companion jar", it should read the system capabilities directly.
See https://www.eclipse.org/lists/equinox-dev/msg09123.html and https://www.eclipse.org/lists/equinox-dev/msg09127.html for technical hints.
Comment 1 Christoph Laeubrich CLA 2020-07-21 12:45:00 EDT
Sounds good, that would imply that system packages could only be resolved if a "true" jdk of that EE is available right?
Comment 2 Mickael Istria CLA 2020-07-21 12:49:13 EDT
(In reply to Christoph Laeubrich from comment #1)
> Sounds good, that would imply that system packages could only be resolved if
> a "true" jdk of that EE is available right?

For system packages, it's already the case; and the idea is to apply the same strategy to system capabilities.
Comment 3 Alexander Kurtakov CLA 2020-09-18 10:34:32 EDT
Mickael, is this done?
Comment 4 Mickael Istria CLA 2020-09-18 10:40:59 EDT
(In reply to Alexander Kurtakov from comment #3)
> Mickael, is this done?

No. Similar work is done for system packages, but not for system capabilities. That said, the value is lower as the capability aren't really so dynamic, the current way we map Java versions/profiles with capabilities is still correct.
Comment 5 Mickael Istria CLA 2021-04-08 18:09:25 EDT
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.