-
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
Add maven.settings property to the test plugins and remove maven.repo in favor of maven.repo.local #15530
Add maven.settings property to the test plugins and remove maven.repo in favor of maven.repo.local #15530
Conversation
@famod I actually can't recall what depends on |
Ok, there is one other issue. |
87a3da2
to
b57dc39
Compare
Well, it was first introduced here (back in 2018): 83a48e9 Occurences in current code:
|
I wonder if this should be set in Codestarts etc. as well? PS: The more system properties we have to set, the more appealing becomes an automatic "bridging" via a Maven extension (the discussion we had just recently). |
I also wonder whether the |
Of course, If it's set by surefire. Sorry, I missed it. I should adjust the bootstrap maven resolver to pick it up directly. |
Ah, thanks. We could just use one property instead of multiple. |
TBH, I do get that it's important that the right local repo ist used, but isn't there more to it? |
Regarding all these properties: I'm +10 to reduce the number of them, to like primarily |
Perhaps, I missed something. What's the evidence of that? |
This: #15513 (comment) |
Sorry, which log is this quoting? |
https://github.com/quarkusio/quarkus/pull/15513/checks?check_run_id=2043450734 |
Thanks @famod Apparently the env vars aren't propagated by the Maven invoker. It seems like we've always had this issue to me. I'll include the fix in this PR. |
@aloubyansky beware though that
It's only an env var because it makes it easier to handle in a GH workflow.
|
b57dc39
to
16ea369
Compare
16ea369
to
f499aee
Compare
I removed |
integration-tests/maven/src/test/java/io/quarkus/maven/it/AddExtensionIT.java
Outdated
Show resolved
Hide resolved
@@ -119,6 +120,7 @@ public MavenProcessInvocationResult execute(List<String> goals, Map<String, Stri | |||
//just running GC | |||
request.setMavenOpts("-Xmx128m"); | |||
} | |||
MojoTestBase.passUserSettings(request); |
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.
In conjunction with https://github.com/quarkusio/quarkus/pull/15530/files#r590560562, maybe that method should be located in some util class in the verifier
package instead of the test base class?
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.
I'm also wondering whether MavenProcessInvoker
should do the same.
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.
That's pretty much where this is used though. I liked the idea of wrapping the invoker. And the RunningInvoker is already overriding execute
.
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.
I don't see MavenProcessInvoker being used directly though.
…m property and the maven settings as mave.settings property
f499aee
to
66cd0da
Compare
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.
LGTM now!
I'm a bit puzzled by localRepository
though, but I'll switch to Zulip to clarify that.
Otherwise devtools tests will be failing to locate the 999-SNAPSHOT artifacts.