5 ms·

mysql-connector-j which us Java devs reference in pom.xml in our Spring Boot projects is open source, GPL2: https://opensource.stackexchange.com/questions/1328

mysql-connector-j which us Java devs reference in pom.xml in our Spring Boot projects is open source, GPL2: https://opensource.stackexchange.com/questions/13287/mysql-connector-j-license https://opensource.stackexchange.com/questions/13287/mysql-c... Where is the ape shit?

papercrane 3y ago
I wouldn't classify it as "ape shit", but the MySQL connector used to be LGPL. Now that's it's GPL any software that bundles it needs to be GPL as well. I'm guessing that Oracle has contacted some companies about commercial licensing. The alternative is to just use the MariaDB connector, which is still LGPL and is MySQL compatible.
- forty 3y ago
  As long as you keep you do not give your server side software to other people, GPL should be fine, right?
  - papercrane 3y ago
    If you're not distributing your software, then yes, it's fine. It's mainly an issue for companies who license their software to other companies. Even if you don't distribute your software it's good to be at least aware of your bill-of-materials. If your company decides to pivot and start licensing out the software then you want to be able to flag any issues like this quickly.
skrause 3y ago
GPL forbids you from using this library in a commercial product (any product that doesn’t use a compatible FOSS license) without buying a commercial license from Oracle. The PostgreSQL JDBC driver doesn’t present this problem to you.
- papercrane 3y ago
  You can use it in a commercial product, but if you distribute the commercial product it's going to require you to adhere to the GPL, which obviously has practical implications. You can use it in an internal product that you use commercially, even if the program interacts with external users (e.g. web server) which is a big reason why AGPL exists. Although, it's best to aware of what internal tools and software may require GPL distribution. For example it's the position of the FSF that distribution of internal tools to contractors requires adherence to the GPL. https://www.gnu.org/licenses/gpl-faq.html#InternalDistribution https://www.gnu.org/licenses/gpl-faq.html#InternalDistributi...

papercrane 3y ago

I wouldn't classify it as "ape shit", but the MySQL connector used to be LGPL. Now that's it's GPL any software that bundles it needs to be GPL as well. I'm guessing that Oracle has contacted some companies about commercial licensing. The alternative is to just use the MariaDB connector, which is still LGPL and is MySQL compatible.

forty 3y ago
As long as you keep you do not give your server side software to other people, GPL should be fine, right?
- papercrane 3y ago
  If you're not distributing your software, then yes, it's fine. It's mainly an issue for companies who license their software to other companies. Even if you don't distribute your software it's good to be at least aware of your bill-of-materials. If your company decides to pivot and start licensing out the software then you want to be able to flag any issues like this quickly.

skrause 3y ago

GPL forbids you from using this library in a commercial product (any product that doesn’t use a compatible FOSS license) without buying a commercial license from Oracle. The PostgreSQL JDBC driver doesn’t present this problem to you.

papercrane 3y ago
You can use it in a commercial product, but if you distribute the commercial product it's going to require you to adhere to the GPL, which obviously has practical implications. You can use it in an internal product that you use commercially, even if the program interacts with external users (e.g. web server) which is a big reason why AGPL exists. Although, it's best to aware of what internal tools and software may require GPL distribution. For example it's the position of the FSF that distribution of internal tools to contractors requires adherence to the GPL. https://www.gnu.org/licenses/gpl-faq.html#InternalDistribution https://www.gnu.org/licenses/gpl-faq.html#InternalDistributi...