And for those who are not convinced:


Le 12/06/2018 à 18:15, Jacques Le Roux a écrit :
That's not serious, remains a legal issue as explained at

<<This answer is also applicable to iTextSharp versions lower than iTextSharp Some people claim that they use iText 4.2.0, but that version has never been officially released.>>

Our users deserver better than saying that I could fix BIRT. You did not get 
it, there is nothing to fix in BIRT.

It's unrelated. We speak about a clear dependency in framework to iText 4.2.0 


Le 12/06/2018 à 15:54, Taher Alkhateeb a écrit :
to qualify: +1 on excluding the transitive dependency after testing
that it works

On Tue, Jun 12, 2018 at 4:44 PM, Taher Alkhateeb
<> wrote:
I'm no longer interested in discussing this, I already explained it.

-1 on the comment
-1 on the removal
+1 on excluding the transitive dependency

If you want to fix things for BIRT, I recommend you do it _outside_
the framework.

On Tue, Jun 12, 2018 at 4:36 PM, Jacques Le Roux
<> wrote:
Le 12/06/2018 à 14:21, Jacques Le Roux a écrit :
com.lowagie.text.* is included in the 3.6.1 BIRT runtime jar that we use,
and there is a legal agreement between the BIRT team and Bruno Lowagie to
use this version[1].
To be clear here, as you (Taher) outlined, we still need to have in our main
/compile 'com.lowagie:itext:2.1.7' // don't update because of license


Reply via email to