You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there is no easy way to get things right and there are many confusing options to control behavior.
This should be reworked/harmonized in the following way (we assume that if a bundle does not define any BREE the current running JVM will be the BREE):
For the target platform (dependency resolution) the EE should be the highest found including toolchains and build JVMs if not configured (e.g. in mojo configuration or target files), if there is any clash then a warning should be given and the highest configured one is used
For the compilation phase (target/source levels) we should always use the BREE in the bundle, there should be an option to either ignore, warn or fail if any of the dependencies use as higher BREE as the bundle (warning is the default)
For execution phase (e.g. tests) if there is an explicit configuration (e.g. in mojo configuration or target files) this should be used, otherwise the BREE of the bundle should be used. There should be an option to either ignore, warn or fail if any dependency has higher BREE (with error as default).
For updatesites we should not use / publish any BREE at all if not explicitly configured.
Also we should revisit all options in this area and possibly deprecate/remove them.
The text was updated successfully, but these errors were encountered:
Currently there is a quite unfortunate mixing of concerns when it comes to determine the desired EEs and as all of them effectively boil down to
there is no easy way to get things right and there are many confusing options to control behavior.
This should be reworked/harmonized in the following way (we assume that if a bundle does not define any BREE the current running JVM will be the BREE):
Also we should revisit all options in this area and possibly deprecate/remove them.
The text was updated successfully, but these errors were encountered: