Build failed in Hudson: Tika-t runk » Apache Tika parsers #320

See -- [INFO] [INFO] Building Apache Tika parsers [INFO]task-segment: [clean, deploy] [INFO

Build failed in Hudson: Tika-trunk #320

See Changes: [nick] When building ISO8601 dates, ensure we're always working in UTC (for TIKA-451) -- [...truncated 59 lines...] [INFO] Retrieving previous metadata from apache.snapshots.h

buildbot success in ASF Buildbot on tika-trunk

The Buildbot has detected a restored build of tika-trunk on ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tika-trunk/builds/53 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: Build Source Stamp: [branch tika/trunk] 964376 Bl

Hudson build is back to normal : Tika-trunk #321

See

Re: Packages and attributes

On Wed, 14 Jul 2010, Paul Jakubik wrote: I created a wiki page for this discussion ( http://wiki.apache.org/tika/MetadataDiscussion). I don't know if that is what you were thinking of. Looks good to me! Having looked through your proposed solutions, I can't see easy ways to implement these us

Re: Packages and attributes

Hi, On Thu, Jul 15, 2010 at 1:14 AM, Paul Jakubik wrote: > I'm hoping that the developers can quickly reach a consensus on how to > change the metadata handling so users can get to metadata for nested > documents. The way I recommend is to pass a custom Parser implementation through the ParseCon

Re: Packages and attributes

On Thu, Jul 15, 2010 at 6:43 AM, Jukka Zitting wrote: > The way I recommend is to pass a custom Parser implementation through > the ParseContext. This gives you detailed access to each component > document. > > You noted that this approach wouldn't work for recursive metadata. Why? > > I didn't th

Re: Packages and attributes

On Thu, Jul 15, 2010 at 6:30 AM, Nick Burch wrote: > > Having looked through your proposed solutions, I can't see easy ways to > implement these use cases: > * enumerate all the Metadata objects at this depth > eg top level has one Metadata object (for the parent file), 1 level > down may have

MediaType.getParameters return type

We ran into an issue recently, where some Bixo code built against Tika 0.7 broke when we tried to use it with Tika 0.8 The problem is that MediaType.getParameters was changed to return a SortedMap versus a Map, so the routine that Bixo is trying to call doesn't exist. We could fix this by b

Re: Packages and attributes

On Thu, Jul 15, 2010 at 6:43 AM, Jukka Zitting wrote: > The way I recommend is to pass a custom Parser implementation through > the ParseContext. This gives you detailed access to each component > document. > > I looked at the code a little further, and I don't see exactly how I can do this. I am