Looks like we were too fast with this step.
Need to be careful not to violate Oracle License agreement.
Instead of adding the binaries to the product, we probably need to have those dependencies listed as requirements in documentation?
I'm no expert on licensing matters, so you either need to do research on that or find someone who knows :)

I read a bit about the Oracle licensing. For the moment I think it would be safest if we don't provide ojdbc and orai18n binaries with the cli but request the users to download them on their own.

I know this is terrible from usability perspective, but if you provide Oracle binaries you have to enforce your own endusers to accept the Oracle Binary licence - which we don't and can't.

I think we have to stay the safe way or write an installer which enforces the user to download the jars with their own oracle account during installation process...