This makes sense. I think providing an "all" jar with all the parsers will
be convenient for new developers. The modular parsers would give more
developers a means to insulate themselves from changes and upgrades to
other parsers. This is currently not available when all of the parsers are
Hi,
I think Chris actually mentioned that this could be something targeted for
a 2.0 release. The first step towards that would be to create the 2.0
branch since I think this might be a big enough effort to not want to block
the trunk ( or master if we move to git). Would the list agree that
[
https://issues.apache.org/jira/browse/TIKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15031879#comment-15031879
]
Chris A. Mattmann commented on TIKA-1804:
-
Hi [~puntogil] [~gagravarr] - Nick answered and beat me
[
https://issues.apache.org/jira/browse/TIKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved TIKA-1804.
-
Resolution: Not A Problem
Per http://www.apache.org/legal/resolved.html#json
> Tika use
Tim,
Fully agreed. One solution that presents itself to me is to finish
up the Git discuss (which was overwhelmingly positive, and I need
to write a wiki page for Nick), get that VOTE out of the way, move
to Git, then basically have two main branches of development. I’d
like 1.x to continue
Sure that’s fine Bob - we don’t need it to be gated on Git.
Create a 2.x branch and go to town, +1 from me :)
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion
Chris,
Looks like we're on the same page :).
- Bob
On Mon, Nov 30, 2015 at 9:08 AM, Bob Paulin wrote:
> Hi,
>
> I think Chris actually mentioned that this could be something targeted for
> a 2.0 release. The first step towards that would be to create the 2.0
> branch
+1
Thanks to Bob for moving forward on this, it's definitely needed.
As one example, the growing list of dependencies is making it increasingly hard
to build a reasonable size job jar for processing the sub-set of all docs we
care about in a web crawl.
-- Ken
> From: Bob Paulin
> Sent:
On Mon, 30 Nov 2015, Allison, Timothy B. wrote:
Perhaps we could start with a tika-advanced-bundle to gather all of the
nlp/advanced parsers? Or would this have to wait for Tika 2.0?
I've noticed that there have been a lot fewer queries (on our list, on
stackoverflow, at events etc) caused
Created 2.x Branch.
https://svn.apache.org/repos/asf/tika/branches/2.x
On 11/30/2015 3:12 PM, Bob Paulin wrote:
This makes sense. I think providing an "all" jar with all the parsers
will be convenient for new developers. The modular parsers would give
more developers a means to insulate
As most of you probably know FOSDEM 2016 (the biggest,
100% free open source developer conference) is right
around the corner:
https://fosdem.org/2016/
We hope to have an ASF booth and we would love to see as
many ASF projects as possible present at various tracks
(AKA Developer rooms):
[
https://issues.apache.org/jira/browse/TIKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15031694#comment-15031694
]
gil cattaneo commented on TIKA-1804:
Hi
It did not surprise me much, ASL license then follow your
gil cattaneo created TIKA-1804:
--
Summary: Tika use no free json.org
Key: TIKA-1804
URL: https://issues.apache.org/jira/browse/TIKA-1804
Project: Tika
Issue Type: Bug
Reporter: gil
[
https://issues.apache.org/jira/browse/TIKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15031681#comment-15031681
]
Nick Burch commented on TIKA-1804:
--
The JSON license has been approved for use by Apache Projects by the
All,
I'm extremely grateful for all of the new nlp +image processing parsers that
we're adding. Might it be time to start down the implementation path to more
modular parser bundles?
Perhaps we could start with a tika-advanced-bundle to gather all of the
nlp/advanced parsers? Or would
15 matches
Mail list logo