-
Notifications
You must be signed in to change notification settings - Fork 83
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
Force qualifier update in org.eclipse.pde.api.tools #1467
Force qualifier update in org.eclipse.pde.api.tools #1467
Conversation
This is usually because one needs to deploy/use a more recent compiler see for example: |
Test Results 285 files ±0 285 suites ±0 57m 32s ⏱️ + 3m 54s For more details on these errors, see this check. Results for commit 45d01d3. ± Comparison against base commit ef694eb. ♻️ This comment has been updated with latest results. |
ae3551c
to
8266f69
Compare
Thanks for that hint. That makes sense and fits to #1461. I updated this PR to verify this in PDE, but if it's fixing it it should be done in the parent-pom as in the linked issue. |
8266f69
to
b7c709a
Compare
This test was successful and the generalization is done in eclipse-platform/eclipse.platform.releng.aggregator#2538. |
b7c709a
to
e333c6d
Compare
Reopened this to try out if a range works well for the |
e333c6d
to
45d01d3
Compare
to fix comparator errors/warnings in verification builds:
But since the I-build does not complain I fear it's a configuration difference and it will be a reoccurring issue.