| Summary: | Remove system capabilities from Java 9+ profiles (read dynamically) | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Mickael Istria <mistria> |
| Component: | Tycho | Assignee: | 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
Sounds good, that would imply that system packages could only be resolved if a "true" jdk of that EE is available right? (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. Mickael, is this done? (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. 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. |