You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@tika.apache.org by Shinichiro Abe <sh...@gmail.com> on 2011/05/10 09:39:22 UTC
Dependency policy
Hello.
For example, I used Tika0.8 (POI-3.7, pdfbox-1.3.1).In fact I used solr3.1.
But it raised a text extraction error in a special excel.
This issue seemed to be fixed at POI-3.8Bata2.
At this time, Can I replace POI with POI-3.8Bata2?
Is it compatible?(I tried to replace it, it worked without error.)
Do developer and user allow to change another version files?
i want to know how to resolve the issue about dependency jar files.
If above things happened, is there a policy we should do?
Regards,
Shinichiro Abe
Re: Dependency policy
Posted by Shinichiro Abe <sh...@gmail.com>.
Hi. I will try to back port and check the working.I understood.
Thank you.
Shinichiro Abe
On 2011/05/10, at 22:47, Nick Burch wrote:
> On Tue, 10 May 2011, Shinichiro Abe wrote:
>> But, Is it okay or be able to allow that POI 3.8 beta 2 on Tika0.8, not POI 3.7 on Tika0.8?(I do not want to use the latest Tika0.9 trunk)
>
> You might need to back port some bits. You could give it a try and see if it compiles, and see if the tests pass. Otherwise, you'd have a much easier time if you did upgrade though - there are other bug fixes (not just around POI) in newer versions
>
> Nick
Re: Dependency policy
Posted by Nick Burch <ni...@alfresco.com>.
On Tue, 10 May 2011, Shinichiro Abe wrote:
> But, Is it okay or be able to allow that POI 3.8 beta 2 on Tika0.8, not
> POI 3.7 on Tika0.8?(I do not want to use the latest Tika0.9 trunk)
You might need to back port some bits. You could give it a try and see if
it compiles, and see if the tests pass. Otherwise, you'd have a much
easier time if you did upgrade though - there are other bug fixes (not
just around POI) in newer versions
Nick
Re: Dependency policy
Posted by Shinichiro Abe <sh...@gmail.com>.
Thank you for your reply.
The general process with POI, I understand.
But, Is it okay or be able to allow that POI 3.8 beta 2 on Tika0.8, not POI 3.7 on Tika0.8?(I do not want to use the latest Tika0.9 trunk)
Does it have possibilities that sometimes it does not work for updating the API use at one of the parts?
Shinichiro Abe
On 2011/05/10, at 18:07, Nick Burch wrote:
> On Tue, 10 May 2011, Shinichiro Abe wrote:
>> For example, I used Tika0.8 (POI-3.7, pdfbox-1.3.1).In fact I used solr3.1.
>> But it raised a text extraction error in a special excel.
>> This issue seemed to be fixed at POI-3.8Bata2.
>> At this time, Can I replace POI with POI-3.8Bata2?
>
> You'd probably want to move to the latest Tika from svn trunk - that uses POI 3.8 beta 2.
>
>> Is it compatible?(I tried to replace it, it worked without error.)
>
> The general process with POI is:
> * new feature / fix is committed to POI
> * patch is posted to let Tika use that
> * new POI release comes out
> * Tika is upgraded to the new POI release, and patch applied
>
> Mostly the changes to Tika with a new POI release are to take advantage of new features, but sometimes its to update the API use to match a change
>
> Nick
Re: Dependency policy
Posted by Nick Burch <ni...@alfresco.com>.
On Tue, 10 May 2011, Shinichiro Abe wrote:
> For example, I used Tika0.8 (POI-3.7, pdfbox-1.3.1).In fact I used solr3.1.
> But it raised a text extraction error in a special excel.
> This issue seemed to be fixed at POI-3.8Bata2.
> At this time, Can I replace POI with POI-3.8Bata2?
You'd probably want to move to the latest Tika from svn trunk - that uses
POI 3.8 beta 2.
> Is it compatible?(I tried to replace it, it worked without error.)
The general process with POI is:
* new feature / fix is committed to POI
* patch is posted to let Tika use that
* new POI release comes out
* Tika is upgraded to the new POI release, and patch applied
Mostly the changes to Tika with a new POI release are to take advantage of
new features, but sometimes its to update the API use to match a change
Nick