-
Notifications
You must be signed in to change notification settings - Fork 229
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
base: main
Are you sure you want to change the base?
Conversation
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? |
I guess all repos require to be updated e.g. https://github.com/apache/incubator-kie-drools/pull/5835/files |
Thanks @RishiRajAnand As @yesamer said, we have to be sure that this is replicated all over our repos. 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 ^^ |
Draft PR for kie-tools: apache/incubator-kie-tools#2871 |
@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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks @RishiRajAnand !
Yes |
@tiagobento |
@gitgabrio That's for building |
Many thanks for submitting your Pull Request ❤️!
Closes/Fixes/Resolves #ISSUE-NUMBER
Description:
Please make sure that your PR meets the following requirements:
Issue-XYZ Subject
[0.9.x] Issue-XYZ Subject
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.