I don't think that shipping drivers is a good idea for the following reasons (skipping already mentioned licensing problems):
1) Some drivers targeting specific databse version. 2) There could be different types of JDBC drivers available for the same database (e.g. JDBC3, JDBC4, alternate implementations, etc.). 3) Some drivers require installation (e.g. MS SQL requires some DLLs to be placed in specific folder). 4) We would have to bother with updating drivers along with their new version releases. It shouldn't be a problem for a user to setup a JDBC driver manually as virtually any developer knows how to do that. Vladimir. On Wed, Jan 14, 2015 at 1:03 PM, Alexey Kuznetsov <[email protected]> wrote: > Hi All! > > I'm working on small GUI utility Schema load (see IGNITE-32 issue > <https://issues.apache.org/jira/browse/IGNITE-32>). > > And for users usability it will be nice to provide JDBC drivers for most > popular databases (Oracle, DB2, MS SQL, ...). > > But I'm afraid that providing proprietary software as part of Apache > download will violate Apache rules. > > We could provide the file with collection of download links, but manual > download is inconvenient for end-user. > > Please advice how we could handle this? > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com >
