iText 5 is under AGPL-license

[GoogleCodeExporter]

I see you started changing to itext5. Do you have in mind that it's under 
AGPL-License? I don't think it's compatible with MIT-License.

Original issue reported on code.google.com by opensour...@gmail.com on 14 Jun 2014 at 9:10

[GoogleCodeExporter]

Hi,

At first XDocReport odt->pdf and docx-pdf converters are based on iText 2.7 and 
not to iText5.

After, please read 
https://code.google.com/p/xdocreport/wiki/WhichLicenseApplies to know which 
license you must apply.

Regards Angelo

Original comment by angelo.z...@gmail.com on 14 Jun 2014 at 10:15

• Changed state: Accepted

[GoogleCodeExporter]

Thanks for clarification. I know iText2.7 was LGPL which is easier to use in 
commercial projects.  AGPL is really strong, so I would recommend to look twice 
if you really need the new features. The issue was  written because I saw 
https://code.google.com/p/xdocreport/source/detail?r=99f4126409af22c46ffbcaa6bf6
0d6224506da6d. 
Anyway, feel free to use it, I only want to give you the hint. Many projects 
are not aware of the license change. For me it's not a problem.

Niels

Original comment by opensour...@gmail.com on 14 Jun 2014 at 4:32

[GoogleCodeExporter]

Ooops sorry, I didn't know that pascal has started support too with IText 5, 
that's very cool pascal:)

Pascal knows very good license about iText, so we will clarify license. 

@Pascal : when you will finish support with IText 5, could you update 
https://code.google.com/p/xdocreport/wiki/WhichLicenseApplies

Many thank's!

Original comment by angelo.z...@gmail.com on 14 Jun 2014 at 5:10

[GoogleCodeExporter]

Just for curiosity, can you explain what the advantages of iText5 are compared 
with iText2.7?
Regards
Niels

Original comment by opensour...@gmail.com on 14 Jun 2014 at 6:22

[GoogleCodeExporter]

Hi all,

I start to work on iText 5 support to allow users to use product with 
professionnal support (there is no support on iText 2.1.7 anymore).

We will keep iText 2.1.7 based converters anyway.

It won't affect XDoceport license as we don't bundle iText 5 (It's only a 
compilation dependency).

Of course if a user wants to use iText 5 support he will have to comply with 
AGPL license.

Regards

Original comment by pascal.leclercq on 16 Jun 2014 at 9:59

[GoogleCodeExporter]

Original comment by angelo.z...@gmail.com on 7 Aug 2014 at 6:06

• Changed state: Done

[GoogleCodeExporter]

Hi,
when will the refactoring and binding of the iText 5 version for the converters 
be finished? 

Should it be possible to split the converter projects to get only the 
commercial Text 5 version interfaced?  Maybe in parallel of the old 2.1.7 
version? We want to have only one iText version in use and I bet it is planned.

I think XDocReport should be keep out legacy code for better quality and comply 
with legal requirements modular.

We plan to use this fantastic looking software stack together with the iText 5 
version we already have purchased.

Thank you all for that great work!

Kind regards,
Andreas

Original comment by nieme...@googlemail.com on 10 Aug 2014 at 9:10

[GoogleCodeExporter]

Hi,

see my comments below...

when will the refactoring and binding of the iText 5 version for the converters 
be finished? 
-> Not sure when, probably not before late september (I'm off until end of 
August).
I think XDocReport should be keep out legacy code for better quality and comply 
with legal requirements modular.
-> I do think exactly the same..

Thank you all for that great work!

-> Thanks

Original comment by pascal.leclercq on 11 Aug 2014 at 11:13

• Changed state: Accepted

[GoogleCodeExporter]

On the other hand have the users in mind, which couldn't switch to iText5 for 
license reason, but are user of XDocReport. So at least the old PDF-Converter 
should be get available.

Original comment by opensour...@gmail.com on 12 Aug 2014 at 6:43

[GoogleCodeExporter]

Sure, we will provide an iText converter for iText 2.1.7 with no dep on iText 5 
and another module based on iText 5+ with no dep on iText 2.1.7.

First of all, I need to remove java.awt.Color from 
org.apache.poi.xwpf.converter.core and create our own Color abstraction.
Next step is to create a converter from our abstraction to java.awt.Color 
indise iText 2.1.7 extension 
and a converter to com.itextpdf.text.BaseColor from iText 5+

Original comment by pascal.leclercq on 29 Aug 2014 at 9:21