Ability to provide classloader for JdbcDatabaseContainer

[npetzall]

Would be nice if one could supply a Driver classloader to the JdbcDatabaseContainer.

This is more or less specific to Oracle test container. Since it's problematic to have the proprietary drivers in a repository.

[npetzall]

Haven't checked might be possible if it used thread context classloader.

[npetzall]

Ok to do PR?

[kiview]

Everyone I know who is working with Oracle JDBC drivers has them in their own Artifactory or deploys them in the local Maven repository on the dev machines. So TBH, I'm not sure if this would help a lot.

Could you explain your use case?

[npetzall]

Use-Case:
I'm helping out on a project SchemaSpy which is open-source. We would like to be able to test Oracle.
We don't want to put oracle driver on the classpath. Since one might assume it will exist on the classpath.

So we/I want to have the driver side-loaded.

[npetzall]

For instance, you could in this project assume that the Oracle driver was located in ${project.baseDir}/proprietary and run Oracle tests when the driver is located in that folder. If the assumption passes. If it can't find the driver it will just ignore the test, which differs from right now as it ignores the whole module.

[npetzall]

No reason to keep this open if it's not wanted.

[kiview]

Let's wait for the opinion of @rnorth.

[rnorth]

I'm sorry, to be honest with this one I think it's just a bit too much complexity to add. Would you be able to find another way to do this? Sorry, but thanks for taking the time to suggest it.

[npetzall]

@rnorth
Yepp, I've done it in my fork and I've got jitpack so I'm good.

[npetzall]

@rnorth manage to solve it with maven and a cpl of settings for the failsafe plugin.
So solving 343 and we can retire the fork.
Might be able to create custom launcher for IDE so it can be run from IDE.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

[stale]

This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case.