Bug 569679

Summary:	Overenthusuiastic execution environment should be at least diagnostic
Product:	[Eclipse Project] Platform	Reporter:	Ed Willink <ed>
Component:	UI	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.18
Target Milestone:	---
Hardware:	PC
OS:	Windows 10
Whiteboard:

Description Ed Willink

2020-12-12 10:12:14 EST

Eclipse OCL is installable from Oxygen onwards and is tested as such. Consequently the MANIFEST.MF BREEs must be compatible with Oxygen - typically BREE 8.

However in order to develop code and detect paltform deprecations it is necessary to use Java 11 and a recent platform for development.

Consequently every MANIFEST.MF has a 

"One of the plug-in's dependencies requires an execution environment of JavaSE-11, hence this plug-in's execution environment should be at least JavaSE-11."

This is not true. The lowerbound of the dependencies accommodates Oxygen and so the plugin's declared dependencies require only what the transitive lowerbound mandates, not what the target platform happens to provide. (Just the same as specifying Java 5 class compatibility is quite acceptable with a Java 11 compiler.) 

Either the "warning" should be at most an "info", or the manifest editor should offer a separate stronger slower Validate action that uses the transitive lowerbounds to use the actual transitive dependencies of plugins to give a truthful diagnostic.