Can I distribute the vtd-xml Java JAR (uses a GPLv2 license) with my commercial product and keep my product closed-source?
<p>Can I distribute vtd-xml with my commercial product without having to share my source code?</p>

<p>I came across this article and now I'm really confused: <a href="https://opensource.com/law/14/7/lawsuit-threatens-break-new-ground-gpl-and-software-licensing-issues" rel="nofollow noreferrer">https://opensource.com/law/14/7/lawsuit-threatens-break-new-ground-gpl-and-software-licensing-issues</a></p>

<p>Do I need to pay for a license from the creators (Ximpleware: <a href="http://www.ximpleware.com/" rel="nofollow noreferrer">http://www.ximpleware.com/</a>)?</p>

<p>If I do have to pay for a license, is there a way around it? Can I offer the vtd-xml JAR as a separate download that the user then puts into a lib directory for my application?</p>

<p>I'm a Software Engineer and not a lawyer, so all this legalise is driving me crazy. Any help would be appreciated. Thanks!</p>

<p>I'll answer the following questions, which hopefully give you a good idea of your situation:</p>

<ol>
<li>If you use vtd-xml (which uses a GPL license), must your product also use gpl?</li>
</ol>

<p>Yes. You can still sell your product, but it will automatically use gpl.</p>

<ol start="2">
<li>What does it mean if your product uses gpl?</li>
</ol>

<p>If your product is being publicly distributed (sold, offered to the public as a free download, etc) then you must make it open source. This doesn't mean you have to have a link to your product's source code available on your website, but if it is requested by someone you must be able to send them a copy of your source code</p>

<p>If your product isn't being publicly distributed (e.g only used by yourself or inside your own company) then you don't have to make your code open source. But obviously you can't sell your code if you don't distribute it.</p>

<p>Note that this is what the current court battle described in <a href="https://opensource.com/law/14/7/lawsuit-threatens-break-new-ground-gpl-and-software-licensing-issues" rel="nofollow noreferrer">https://opensource.com/law/14/7/lawsuit-threatens-break-new-ground-gpl-and-software-licensing-issues</a> is about. Ximpleware argues that ameriprise are distributing a product, and therefore needs to make their code open source due to the copyleft requirement of the gpl</p>

<ol start="3">
<li>You want to sell your product, but not make it open source. What do you do?</li>
</ol>

<p>You need to contact ximpleware and buy a commercial license to use their code. (their homepage has contact details for this). After that, you are free to use their code and not have to make your application open source</p>

<ol start="4">
<li>You want to sell your product, not make it open source, but also not buy a commercial license from Ximpleware. What do you do?</li>
</ol>

<p>You can theoretically make a piece of independant code, sell it, and give instructions for your users to download Ximpleware's code and incorporate it into your program. This is quite a roundabout way, and potentially a legal grey area (since I can see Ximpleware arguing that people would do this to avoid making their programs open source or paying for a commercial license, but this is probably a problem that you won't have to face unless Ximpleware finds it financially worth it to sue your company for, and even then it's a difficult case)</p>

<p>Overall, buying a commercial license from ximplewar would be the most "cleanest way" to go about things, but as it stands I don't think there is anything illegal with selling your software and requiring clients to download vtd-xml separately</p>

software gpl