-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Update Maven to 3.8.6, maven-wrapper to 3.1.1 and maven-invoker to 3.2.0 #26086
Conversation
.../maven-resolver/src/main/java/io/quarkus/bootstrap/resolver/maven/BootstrapMavenContext.java
Show resolved
Hide resolved
@@ -48,7 +48,7 @@ public InvocationResult execute(InvocationRequest request) throws MavenInvocatio | |||
|
|||
File workingDirectory = getWorkingDirectory(); | |||
if (workingDirectory != null) { | |||
cliBuilder.setWorkingDirectory(getWorkingDirectory()); | |||
cliBuilder.setBaseDirectory(getWorkingDirectory()); |
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.
See apache/maven-invoker@ca84e5c#diff-7a2ee223cf0ee38d98ed325df11438abe1b5134ce5d7430933461efc0ff5963cL725
I think this change should be ok given the way Quarkus is using this method.
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.
This is a breaking API change though, isn't it? Does this code work with Maven 3.8.6 w/o this change?
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.
This is a change in maven-invoker
, not in actual Maven, so I don't think Maven < 3.8.6 will have a problem with this.
Should I break this up into three PRs?
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.
Should be OK then, given that it's managed in the quarkus-bom.
Good candidate for 2.10.0 AFAICS, but too bad it comes too late for CR1. |
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.
Thanks @famod
This comment has been minimized.
This comment has been minimized.
@gsmet any objections? |
I'll go ahead and merge this. |
I think this PR should have noteworthy (or breaking change ) label. And probably migration guide entry.
We have seen two kinds of troubles A) failures with consul extension - quarkiverse/quarkus-config-extensions#70 B) usage of jsoup in tests, jsoup was transitive dependency of |
Hmmm, let's not backport it then. |
Thanks for noticing @rsvoboda We'll need to check whether we still want to manage jsoup in the quarkus-bom. |
I think we shouldn't. JSoup sometimes have CVE so I would rather avoid it if we don't have a dependency on it. |
So the idea is to:
❓ |
If we are not depending on it, yes. Now I'm a bit unclear if we are still dragging it in some cases? |
The extension processor uses it. I would say yes to your plan @famod. Were you planning to take care of that? |
I created #26141 for jsoup in the morning, these discussions should be probably moved there |
about |
True, the bootstrap doesn't use it any more though. |
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12351556
is the one that caused Quarkus to not update to 3.8.5.
PS: Bumping wrapper and invoker is not mandatory, but I saw those were outdated and just updated them as well.