On 2/5/2015 17:59 PM, mkl wrote:
> "just" in this case is merely more than a year ago...
And the situation that is described, where the customer stopped working
with the integrator, was a situation where the integrator had introduced
the AGPL version of iText in a situation that either required h
codemeister2 wrote
> What you just described is called tortious interference or interference
> with contractual relations...
"just" in this case is merely more than a year ago...
--
View this message in context:
http://itext-general.2136553.n4.nabble.com/Use-of-iTextSharp-dll-4-1-6-tp4659543p
On 2/5/2015 17:02 PM, codemeister2 wrote:
> What you just described is called tortious interference or interference with
> contractual relations. Calling up someone's client and telling them their
> integrator did something wrong or bad by using the older, more liberally
> licensed version of iText
What you just described is called tortious interference or interference with
contractual relations. Calling up someone's client and telling them their
integrator did something wrong or bad by using the older, more liberally
licensed version of iTextSharp can constitute civil malfeasance under the
l
> But if the application is referencing the dll with version 4.1.6.0 then we
> can still continue using the same right even after new release? if somebody
> is happy with the old version and don't feel need to upgrade it to newer
> version can still use 4.1.6.0 version under the MPL and LGPL licens
On 12/12/2013 12:39 PM, TestUser wrote:
> if somebody is happy with the old version and don't feel need to
> upgrade it to newer version can still use 4.1.6.0 version under the
> MPL and LGPL licenses, which allowed them to be used in closed-source
> software projects.
It depends.
Do you have
Thanks for the quick response.Yes i got your viewpoint.But if the application
is referencing the dll with version 4.1.6.0 then we can still continue using
the same right even after new release? if somebody is happy with the old
version and don't feel need to upgrade it to newer version can still u
On 12/12/2013 11:25 AM, Anita wrote:
> We planning to use iTextSharp-4.1.6 DLL. We are not indenting to
> modify any code. We will need to reference the dll. In the site
> "https://github.com/itextsharper/iTextSharp-4.1.6 " it is mentioned,
> this is "The MPL / LGPLv2 version of the iTextSharp l
