-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only apply a better profile if allowed #4553
Only apply a better profile if allowed #4553
Conversation
Marking for Tycho 5 only as it is probably a breaking change, so lets see what all fails now. |
2b70930
to
0d5ceee
Compare
I think the message is quite expected here:
so we probably should update the tests here and then apply the change even to Tycho 4 |
f18003a
to
c282f3a
Compare
Update of the BREEs extracted here: this should then be rebased on the PR to provide the actual fix. |
Currently we have a lot of old integration tests that require different BREEs due to historical reasons even though we already depend on much newer dependencies. This update the BREE of all test that do not explicitly test a specific feature related to the BREE to Java 17 to reflect the things we actually use.
Currently a configured profile is unconditionally replaced by a better one of the current JVM, but this is wrong if not explicitly allowed by the configuration. This is now changed, to be only used if ignoring the BREE is actually enabled.
c282f3a
to
6a45b75
Compare
This should be manually be packported to tycho 4.x as we need to add a special note to the release notes about this possibly braking behavior compared to previous version. |
Currently a configured profile is unconditionally replaced by a better one of the current JVM, but this is wrong if not explicitly allowed by the configuration.
This is now changed, to be only used if ignoring the BREE is actually enabled.