|Date Added:||2 November 2005|
|File Size:||22.81 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Unable to query a db from gradle build script Ask Question. Then I moved the script within a gradle task, no changes on code but loading handled by gradle buildscript statement. Email Required, but never shown.
Subscribe to RSS
Driver” try playing around with that and see if it gets you anywhere Also take a look at this other question: Sign up or log in Sign up using Google. I would like to thank cptwonton that pointed me to a great explanation here.
But that is quite different from Java’s DriverManager not knowing where to find the driver – which is most certainly your issue at hand. The path you provide to classpath files path needs to be a relative path to the root of your jtd project directory.
Unicorn Meta Zoo 9: I had to modify the gradle script a little and this is the working version. It appears that your net. Improving the question-asking experience. This is likely because of an issue with your path in.
jtdsjar Detail –
I launched with groovy QueryTest. Sorry that was not clear. I’d suggest moving your jtds jar into the libs directory, and taking a look at this doc: I omitted the whole path and put some periods. I try to edit and make it clear.
Have you see the docs referenced here? Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. How do we handle problem users?
That’s what the buildscript dependencies classpath files code is for. No suitable driver found for jdbc: Would ask for help. Evelino Bomitali Evelino Bomitali 98 9 9 bronze badges. Also, the jtds jar is ntds the maven repo, why not use that instead of a local jar? Post as a guest Name. Driver” error message is thrown by classloader.
Download jtds JAR 1.2.2 with all dependencies
The beauty of build tools jwr gradle and maven is that you do not need to locally store or manage many popular jars. The reason I am using local jar is that no access to maven or jcenter is possible from that machine.
Then I moved the script within a gradle task, no changes on code but loading handled by gradle buildscript statement import groovy.