Skip to content
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

[m2e] Expand bundle version ranges for M2E imports #5418

Merged
merged 1 commit into from Nov 8, 2022

Conversation

timothyjward
Copy link
Contributor

In recent versions (2022-06 and later) of Eclipse the version of the M2E maven runtime bundle has stopped matching the M2E version and now uses a higher version related to the maven it packages. We need to be able to use this if M2E support is to keep working.

Fixes #5417

Signed-off-by: Tim Ward timothyjward@apache.org

In recent versions (2022-06 and later) of Eclipse the version of the M2E maven runtime bundle has stopped matching the M2E version and now uses a higher version related to the maven it packages. We need to be able to use this if M2E support is to keep working.

Fixes bndtools#5417

Signed-off-by: Tim Ward <timothyjward@apache.org>
Copy link
Member

@bjhargrave bjhargrave left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sigh. This problem is caused by eclipse-m2e/m2e-core@bdf007b which made a significant version change in the m2e bundle version to match the embedded maven runtime version (1.18 => 3.8).

So this change should see us through to Maven 4. 🤞

@timothyjward
Copy link
Contributor Author

Possibly one to make @laeubi aware of as well.

@timothyjward timothyjward merged commit 334a811 into bndtools:master Nov 8, 2022
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bndtools M2E integration broken on latest Eclipse Releases
2 participants