Hi all,
Thank you both guys, my question was about legal issues that you clarified me :)
Reinhard, no problem about the optionals, even if I remember the
policy I appreciate you reminded me it :) BTW, after a quick overview
on Tika, I was thinking about importing just the needed classes and
modifying them according to our needs, so if you agree I'd add the
XInclude in the cocoon-sax module... what do you think about it? Just
let me know!
See you guys and thanks a *lot* for your help :)
Best regards
Simo
On Tue, Nov 24, 2009 at 12:16 PM, Reinhard Pötz <reinh...@apache.org> wrote:
> Simone Tripodi wrote:
>> Hi Sylvain
>> Sorry but I forgot to ask you a short question in the previous email:
>> can the Tika code be imported/modified into Cocoon3?
>
> Do you really have to modify Tika code? If so it would be best to give
> back your contributions to the their project.
>
> Since you have to include a library I strongly recommend that everything
> goes into cocoon-optional in order to keep the number of required
> libraries low for the pipeline API.
>
>> AFAIK it should
>> be allowed, but I don't know the conditions under which it can be
>> done.
>
> If your questions is about licensing, then it's very simple: You don't
> have to do anything because Tika is an ASF project.
>
> --
> Reinhard Pötz Managing Director, {Indoqa} GmbH
> http://www.indoqa.com/en/people/reinhard.poetz/
>
> Member of the Apache Software Foundation
> Apache Cocoon Committer, PMC member reinh...@apache.org
> ________________________________________________________________________
>
--
http://www.google.com/profiles/simone.tripodi
