-
Notifications
You must be signed in to change notification settings - Fork 196
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
compare-versions-with-baseline failing (since 2.7) when executionEnvironment=none #707
Milestone
Comments
Do you think you can derive an integration test for this or small example project to investigate this further? |
I'm working on it and have a minimal test. I'm trying to also implement a fix and hope I can submit them together as a PR before the end of this day. |
mickaelistria
added a commit
to mickaelistria/tycho
that referenced
this issue
Mar 1, 2022
Fix some methods and conditions to better distinguish cases of ee=none vs custom EE. This allows further invocations of TargetPlatformFactoryImpl.createTargetPlatform to work with ee=none.
mickaelistria
added a commit
to mickaelistria/tycho
that referenced
this issue
Mar 1, 2022
Fix some methods and conditions to better distinguish cases of ee=none vs custom EE. This allows further invocations of TargetPlatformFactoryImpl.createTargetPlatform to work with ee=none.
mickaelistria
added a commit
that referenced
this issue
Mar 1, 2022
Fix some methods and conditions to better distinguish cases of ee=none vs custom EE. This allows further invocations of TargetPlatformFactoryImpl.createTargetPlatform to work with ee=none.
akurtakov
added a commit
to akurtakov/corrosion
that referenced
this issue
Mar 2, 2022
mickaelistria
pushed a commit
to eclipse-corrosion/corrosion
that referenced
this issue
Mar 14, 2022
laeubi
pushed a commit
that referenced
this issue
Mar 30, 2022
Fix some methods and conditions to better distinguish cases of ee=none vs custom EE. This allows further invocations of TargetPlatformFactoryImpl.createTargetPlatform to work with ee=none.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using compare-versions-with-baseline mojo on a module which set
<executionEnvironment>none</executionEnvironment>
, the following exception is thrownThis is a regression from 11f7c9d which introduce some execution stacks calling
environmentConfiguration.setFullSpecificationForCustomProfile
multiple times which it's not supposed to happen. One pre-existing issue that can be part of the cause here isExecutionEnvironmentImpl.isCustomProfile
returningtrue
if no EE is to be injected.The text was updated successfully, but these errors were encountered: