If we can migrate it first, I could work on merging back your work into an official release.
On 16 August 2016 at 14:15, Benedikt Ritter <[email protected]> wrote: > Matt Sicker <[email protected]> schrieb am Di., 16. Aug. 2016 um 20:51 Uhr: > > > Is dbutils in git yet? > > > > No, but we can easily migrate it. > > > > > > On 16 August 2016 at 13:46, William Speirs <[email protected]> wrote: > > > > > I was, but am no longer, working on DBUTILS 2.0. There are a LOT of > > changes > > > there. Some of those changes have been made here: > > > https://github.com/wspeirs/sop4j-dbutils I don't cut releases to that > > all > > > that often either, but grabbing that code and getting it working > > shouldn't > > > be too hard. > > > > > > Bill- > > > > > > On Tue, Aug 16, 2016 at 1:57 PM, Matt Sicker <[email protected]> wrote: > > > > > > > Is dbutils even ready for a 2.0 release? If so, I could RM it > sometime > > > > soon. > > > > > > > > On 16 August 2016 at 12:45, Robert Huffman <[email protected] > > > > > > wrote: > > > > > > > > > As nearly as I can tell, the latest release of dbutils is 1.6. > > However, > > > > > there are hints there was a 1.7 at some point, though there is no > > > branch > > > > or > > > > > tag for that version on the GitHub Mirror. The GitHub mirror does > > have > > > a > > > > RC > > > > > for 2.0. > > > > > > > > > > This is an issue for me because our recent upgrade to OJDBC 12 > causes > > > > > AbstractQueryRunner.fillStatement to throw an SQL exception. That > > > defect > > > > > has been resolved, supposedly in 1.6. However, the sources.jar from > > > > > MavenCentral for 1.6 does NOT include the fix. > > > > > > > > > > So I have a couple of questions. Can someone publish the correct > > > > artifacts > > > > > to Maven Central? And when can we expect 2.0 to be released? > > > > > > > > > > > > > > > > > > > > > -- > > > > Matt Sicker <[email protected]> > > > > > > > > > > > > > > > -- > > Matt Sicker <[email protected]> > > > -- Matt Sicker <[email protected]>
