more lenient osgi.ee=JavaSE for unknown JDKs

[chrisrueger]

Closes #6858

Experimental:

For a yet to bnd unknown JDK (e.g. JDK-10000) Instead of

Require-Capability: osgi.ee;filter:="(osgi.ee=UNKNOWN)"

we now create

Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=9955))"

for a .class file with u2 major_version 10000 (9955 == 10000 - 45)

[laeubi]

In the advent of regular Java versions released this seems the right approach. In general the EE enum might needs to be revised by:

1. deprecate it
2. replace all usages by a new JavaExecutionEnvironment class that can hold a java version and computes what ever is needed from that.

[laeubi]

@chrisrueger I have fired up a task for the AI here maybe it produces something useful as a base-ground:

• Refactor EE from enum to class for dynamic Java version support laeubi/bnd#5

[chrisrueger]

In general the EE enum might needs to be revised by

Just adding that currently there are two enums holding Java versions:

• aQute.bnd.osgi.Clazz.JAVA
• aQute.bnd.build.model.EE

[peterkir]

Selecting a ee from bndrun files is a little hard when there are so many list items available. Maybe we can downsize a little.

[chrisrueger]

#6858 add enums up to JDK50 #6891

Feel free to downsize whatever I did in https://github.com/bndtools/bnd/pull/6891/files :)

[laeubi]

Selecting a ee from bndrun files is a little hard when there are so many list items available. Maybe we can downsize a little.

mY recommendation would be to replace dropdowns by a spinner or something instead in the UI