-
Notifications
You must be signed in to change notification settings - Fork 10
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
Jooq into separate tag #13
Jooq into separate tag #13
Conversation
11e86df
to
0229318
Compare
pom.xml
Outdated
@@ -62,7 +67,7 @@ | |||
<mysql-connector-j.version>8.0.32</mysql-connector-j.version> | |||
<mariadb-java-client.version>3.1.2</mariadb-java-client.version> | |||
<assertj-core.version>3.24.2</assertj-core.version> | |||
<maven-plugin-testing-harness.version>3.3.0</maven-plugin-testing-harness.version> | |||
<maven-plugin-testing-harness.version>4.0.0-alpha-1</maven-plugin-testing-harness.version> |
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.
Any reason for using Alpha
version considering alpha releases might be buggy?
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.
No, actually i will return
} | ||
public class PluginTest { | ||
|
||
@Rule |
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.
Is it not possible to use JUnit 5 here? Once we introduce the dependency on JUnit 4 it will be hard to remove later.
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.
Actually AbstractMojoTestCase
extends TestCase
from Junit3 .
Usage of @Rule
make possible to use Junit4 out of the box. I agree that v5 better than v4, but generally there is no difference ,because we have junit-vintage-engine
which gets us backward compatibility.
I'd love to pick Junit5 ,but maven-plugin-testing-harness
does not support 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.
The changes are looking good to me.
The only concern is introducing the dependency on JUnit 4 for testing.
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
Hi @sivaprasadreddy , @lukaseder .
I did suggested approach, may i get your review?
Resolves #12