[
https://issues.apache.org/jira/browse/TIKA-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905363#comment-14905363
]
Hudson commented on TIKA-1657:
--
UNSTABLE: Integrated in tika-trunk-jdk1.7 #853 (See
[https://
+1 to branching. Given some surprises we've had, I'd want to have a
1.12+-SNAPSHOT branch easily available, because I suspect that 2.0 is still at
least 6 months* off given the current pace of progress and what I've seen on
other projects making major release changes. Wish I had more hours in
>>I think Tim has a draft out on this mailing list that would benefit from some
>>additional perspectives. Really cool to be talking about doing this!
Agreed...in 2.0 branch with living 1.12-SNAPSHOT as backup :)
There's still quite a bit to decide...my proposals are still very much strawmen
w
>Tim, was your check for File#getName done manually or it's present in tests
>somehow? If it's >present in tests we can check it on major platforms (I can
>test on linux, win xp and maybe on >macosx) with different jdks.
It was a unit test that initially uncovered the problem -- all worked well
Alexander Pogrenbyak created TIKA-1749:
--
Summary: Upgrade, or shade, guava
Key: TIKA-1749
URL: https://issues.apache.org/jira/browse/TIKA-1749
Project: Tika
Issue Type: Bug
Com
+1 for the branching strategy.
With respect to slicing up the parsers it would be great to have more
discussion on how the parsers should be organized. I think Tim has a draft
out on this mailing list that would benefit from some additional
perspectives. Really cool to be talking about doing thi
It seems to be a good idea to avoid inclusion of commons-io into tika-core
till 2.0 if we will release it in several months.
In this case we will have trunk w/ ongoing development of 2.0-SNAPSHOT and
branch for 1.11+ bugfixes.
Some changes related to java7 can be included to 1.11/1.12 with no prob
I’m not so keen on fundamentally changing the organization of
Tika until 2.x. This seems like a major change to me in the
way people expect to consume Tika.
Can we:
1. Release a 1.11 that doesn’t include these types of changes
2. After 1.11, change trunk to be 2.0-SNAPSHOT and work those
types of
[
https://issues.apache.org/jira/browse/TIKA-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904761#comment-14904761
]
Giuseppe Totaro commented on TIKA-1739:
---
Great suggestion [~gagravarr]. Thanks [~chri
+1 for the uber jar!
Regarding jdk7 issues, I have a few more I will create and patch later
tonight - I'll post a list of issues as well.
On Sep 23, 2015 5:26 PM, "Konstantin Gribov" wrote:
> Tim, was your check for File#getName done manually or it's present in tests
> somehow? If it's present i
[
https://issues.apache.org/jira/browse/TIKA-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904602#comment-14904602
]
Konstantin Gribov commented on TIKA-1743:
-
[~bobpaulin], I have two ideas on the is
Tim, was your check for File#getName done manually or it's present in tests
somehow? If it's present in tests we can check it on major platforms (I can
test on linux, win xp and maybe on macosx) with different jdks.
In case commons-io doesn't support ':' as file separator we can have simple
utilit
[
https://issues.apache.org/jira/browse/TIKA-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904419#comment-14904419
]
Bob Paulin commented on TIKA-1743:
--
I'll put together a patch. Are there other parsers th
Tim Allison created TIKA-1748:
-
Summary: Upgrade to POI 3.13-final when available
Key: TIKA-1748
URL: https://issues.apache.org/jira/browse/TIKA-1748
Project: Tika
Issue Type: Task
Re
Tim Allison created TIKA-1747:
-
Summary: Change file->path in tika-batch throughout
Key: TIKA-1747
URL: https://issues.apache.org/jira/browse/TIKA-1747
Project: Tika
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/TIKA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904388#comment-14904388
]
Tim Allison edited comment on TIKA-1744 at 9/23/15 12:06 PM:
-
T
[
https://issues.apache.org/jira/browse/TIKA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904388#comment-14904388
]
Tim Allison commented on TIKA-1744:
---
Thank you, [~kunda]!
I think this was part of the
[
https://issues.apache.org/jira/browse/TIKA-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904371#comment-14904371
]
Tim Allison commented on TIKA-1743:
---
Oh, I wish I had time to finish off TIKA-1657 and TI
[
https://issues.apache.org/jira/browse/TIKA-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904360#comment-14904360
]
Tim Allison commented on TIKA-1742:
---
The HORROR! If it were a second rate conference, it
[
https://issues.apache.org/jira/browse/TIKA-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904156#comment-14904156
]
Nick Burch commented on TIKA-1739:
--
My view is that {{AutoDetectParser}} is a special kind
20 matches
Mail list logo
