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
[WFLY-19167] war containing JDBC drivers deploys an extra driver #17760
Conversation
Apologies for the spam in the description by the wildfly-bot 😅 . We accidentally had 2 versions deployed, updating one's another actions. Please feel free to remove all the clutter from the description. |
no worries @The-Huginn :) |
|
||
@Test | ||
public void testJdbcDrivers() throws Exception { | ||
String driverName = DEPLOYMENT; |
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.
@gaol maybe it will also be useful to verify the number of deployed drivers? IIUC if there was a short name driver at index '2' the test will pass so maybe we could guard from this....
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.
right, good catch !
will try to get the jdbc driver using short name and it should fail.
checking number of deployed jdbc drivers maybe confusing as we need to filter out the default h2
driver.
updated according to the feedback by checking if the jdbc driver with the short name is not installed. please review again, @tadamski thanks :) |
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.
@gaol LGTM now. Thanks for fixing it!
/retest |
Issue: https://issues.redhat.com/browse/WFLY-19167
More information about the wildfly-bot[bot]