-
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
Look for test classes in the model loaded from the Gradle tooling #29808
Conversation
This comment has been minimized.
This comment has been minimized.
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.
@@ -46,6 +46,7 @@ public QuarkusPluginExtension(Project project) { | |||
} | |||
|
|||
public void beforeTest(Test task) { | |||
project.getLogger().info("QuarkusPluginExtension.beforeTask " + task.getName()); |
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.
Hmmm, do we want to keep that info
log? It looks like a debug message.
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.
The issue is that loading an app model this way is known to be slow. It could take 5 sec, for example, or even longer. I added it just for that reason and because it's only for launching from an IDE use-case.
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.
Well, in that case, it should be a message that an end user can understand such as Loading the application model...
or something similar?
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.
Oh, sorry! I thought of a different info message I added in another place. Yes, this is a leftover, thanks for spotting it!
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, but I agree with @gsmet that the INFO message should be clearer
b347cfb
to
87eb67f
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
With this change, when Quarkus tests are launched from an IDE for Gradle projects as "JUnit tests", test classes will be looked up in directories provided by the application model loaded with the Gradle tooling API.
This kind of class look up should be done for all cases, including Maven. I guess this could be the first step towards that refactoring.