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

NO-ISSUE: Upgrade maven to 3.9.9 #3829

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

RishiRajAnand
Copy link

  • We need to upgrade maven as we found some tests breaks during upgrading quarkus to 3.15 LTS
  • More information on quarkus issue

Many thanks for submitting your Pull Request ❤️!

Closes/Fixes/Resolves #ISSUE-NUMBER

Description:

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Your code is properly formatted according to this configuration
  • Pull Request title is properly formatted: Issue-XYZ Subject
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Issue-XYZ Subject
  • Pull Request contains link to the JIRA issue
  • Pull Request contains link to any dependent or related Pull Request
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

@ricardozanini
Copy link
Member

We also need to upgrade https://github.com/apache/incubator-kie-tools/ and link both PRs, check if everything is ok and then merge both.

Is https://github.com/apache/incubator-kie-kogito-apps/ affected too?

@yesamer
Copy link
Contributor

yesamer commented Jan 21, 2025

I guess all repos require to be updated

e.g. https://github.com/apache/incubator-kie-drools/pull/5835/files

@gitgabrio
Copy link
Contributor

Thanks @RishiRajAnand

As @yesamer said, we have to be sure that this is replicated all over our repos.
IINW, drools repo uses 3.8.6
At the same time, drools depends on Quarkus, so I guess it should also follow the samve modification.

Last (very side note: the common dependencies (as the maven version) should be declared in the top most pom/bom, and then inherited downward

@baldimir ^^

@thiagoelg
Copy link
Member

Draft PR for kie-tools: apache/incubator-kie-tools#2871

@tiagobento
Copy link
Contributor

@gitgabrio All repos that composed the Apache KIE 10.0.0 release are aligned to be on 3.9.6. Maybe READMEs are outdated, but every build verification was supposed to be using 3.9.6 as per our Release Procedure document.

@thiagoelg Thanks! I'll convert this PR to non-draft so that the PR checks run.

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.

7 participants