Well, that error WAS important. It compiles and pretends to work, but does not extract any text or metadata (that's why it is so fast!).
Thank you, Mark On Tue, Aug 30, 2011 at 7:20 PM, Mark Kerzner <[email protected]> wrote: > I do get an error in the build, but it create the core snapshot jar anyway. > Should I be concerned? > > Thank you, > Mark > > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] > /home/mark/ThirdParty/tika-source/tika-site/tika-parsers/src/main/java/org/apache/tika/parser/image/ImageMetadataExtractor.java:[89,34] > error: cannot access JPEGDecodeParam > [INFO] 1 error > [INFO] ------------------------------------------------------------- > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Apache Tika parent ................................ SUCCESS > [32.118s] > [INFO] Apache Tika core .................................. SUCCESS > [15.994s] > [INFO] Apache Tika parsers ............................... FAILURE > [57.498s] > [INFO] Apache Tika application ........................... SKIPPED > [INFO] Apache Tika OSGi bundle ........................... SKIPPED > [INFO] Apache Tika ....................................... SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 2:23.922s > [INFO] Finished at: Tue Aug 30 18:52:20 CDT 2011 > [INFO] Final Memory: 28M/156M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > (default-compile) on project tika-parsers: Compilation failure > [ERROR] > /home/mark/ThirdParty/tika-source/tika-site/tika-parsers/src/main/java/org/apache/tika/parser/image/ImageMetadataExtractor.java:[89,34] > error: cannot access JPEGDecodeParam > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn <goals> -rf :tika-parsers > > > On Tue, Aug 30, 2011 at 7:08 PM, Mark Kerzner <[email protected]>wrote: > >> SUCCESS!!!! >> >> Nick, not only it closes all files, but it feels to work much faster (I >> mean, in the debuggers, real performance may vary :) >> >> Thank you everybody for today's productive discussion and help. >> >> Mark >> >> PS. If anyone every gets sued, they should use FreeEed for eDiscovery and >> come back a winner! >> >> >> On Tue, Aug 30, 2011 at 5:25 PM, Nick Burch <[email protected]>wrote: >> >>> On Tue, 30 Aug 2011, Mark Kerzner wrote: >>> >>>> For the time being, is there a workaround that I could use? Right now, >>>> this >>>> is a show-stopper for my application >>>> >>> >>> Any chance you could do a svn checkout, build, and try with that? After >>> my last email, I have a nagging feeling about the timing of making NPOIFS >>> implement closable... I upgraded the POI dependency earlier today, so it's >>> worth checking with >>> >>> Nick >>> >> >> >
