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

Avoid data-tables, echarts, and prism upper bounds error #2682

Conversation

MarkEWaite
Copy link
Contributor

Avoid data-tables, echarts, and prism upper bounds error

@basil described it in #2680 (comment)

analysis-pom is (incorrectly) pulling in a version of ArchUnit with a requireUpperBounds error, which analysis-pom has (also incorrectly) downgraded from an error to a warning.... Since PCT will automatically resolve requireUpperBoundDeps errors by choosing the newer version, and since the newer version is not ABI-compatible with the older version, the issue occurs.

This workaround should be removed when analysis-pom has been updated to fix the requireUpperBoundDeps error and make requireUpperBoundDeps an error instead of a warning.

Testing done

Confirmed that PLUGINS=echarts-api TEST=InjectedTest bash local-test.sh passes after this change and fails before this change.

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

@basil described it in
jenkinsci#2680 (comment)

> analysis-pom is (incorrectly) pulling in a version of ArchUnit with
> a requireUpperBounds error, which analysis-pom has (also
> incorrectly) downgraded from an error to a warning.... Since PCT
> will automatically resolve requireUpperBoundDeps errors by choosing
> the newer version, and since the newer version is not ABI-compatible
> with the older version, the issue occurs.

This workaround should be removed when analysis-pom has been updated
to fix the requireUpperBoundDeps error and make requireUpperBoundDeps
an error instead of a warning.
@MarkEWaite MarkEWaite requested a review from a team as a code owner November 22, 2023 23:42
@timja timja added the chore Reduces future maintenance label Nov 23, 2023
@timja timja merged commit 92e1dbc into jenkinsci:master Nov 23, 2023
5 checks passed
@MarkEWaite MarkEWaite deleted the workaround-upperbounds-error-in-echarts-and-more branch November 29, 2023 14:07
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Reduces future maintenance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants