Is updating or changing the DatabaseUtils.probs file in the weka.jar a valid work around this limitation?

Are there any other more dynamic solutions to this?



On Wed, Jan 17, 2018 at 11:41 AM Gibran Castillo <gibran.e.castillo@gmail.com> wrote:
One way to configure Weka Workbench to load JDBC driver jar files into the classpath is by adding or installing the Weka Package JDBCDriversDummyPackage using the Weka Package Manager.

Is there any other way to do this?  Is there a location in Weka for Windows 7 OS to drop JDBC driver jar files so that they get loaded into the classpath by the system?

Please advise, thanks!