+1 to file a separate issue, Tim.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-5th floor
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: <Allison>, "Timothy B." <talli...@mitre.org>
Reply-To: "dev@tika.apache.org" <dev@tika.apache.org>
Date: Monday, June 2, 2014 1:22 PM
To: "dev@tika.apache.org" <dev@tika.apache.org>
Subject: Unpacker resource

>Speaking of the unpacker resource, last time I looked, it didn't do full
>recursion on unpacking...I don't think.  It only unpacked the first level
>attachments, but not the attachments of the attachments.  Should I open
>an issue/add to my todo list to make this fully recursive at some point?
>Or, should we wait for input from users?
>
>-----Original Message-----
>From: Nick Burch [mailto:apa...@gagravarr.org]
>Sent: Monday, June 02, 2014 3:35 PM
>To: dev@tika.apache.org
>Subject: Re: JAXRS, endpoints and a / welcome page - any ideas why it's
>broken?
>
>On Tue, 20 May 2014, Sergey Beryozkin wrote:
>>>>> Maybe we should post to users@, and see if anyone says they do?
>>>> 
>>>> Sounds good, please ask or I can do it, let me know please
>>> 
>>> As our jaxrs guru, can you? :)
>>
>> I've just asked at the users list
>
>Based on the silence, I don't think the unpacker resource is very widely
>used. As such, I think we should be fine to push it to the new URL
>pattern 
>as discussed, and mention it in change logs / release notes / etc
>
>Who wants to do the honours? :)
>
>Nick

  • Unpacker resource Allison, Timothy B.
    • Re: Unpacker resource Mattmann, Chris A (3980)

Reply via email to