Skip to content

Conversation

@fipro78
Copy link
Contributor

@fipro78 fipro78 commented Nov 19, 2025

No description provided.

@fipro78 fipro78 force-pushed the issue_175 branch 2 times, most recently from ab89a36 to d6e6927 Compare November 19, 2025 09:24
org.eclipse.jdt.core.compiler.codegen.targetPlatform=17
org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve
org.eclipse.jdt.core.compiler.compliance=11
org.eclipse.jdt.core.compiler.compliance=17
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this API-Breaking? Projects on Java 11 cannot upgrade to 2.7.0.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably yes. But people on Java 11 already can't upgrade to 2.6. At least for some of the extensions. Because the dependencies require Java 17, so the extensions require the same. And the same will apply to the core once the dependency to a newer swt version is introduced to support the new scaling API.

Signed-off-by: Dirk Fauth <dirk.fauth@googlemail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants