[jira] [Commented] (TIKA-1521) Handle password protected 7zip files

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290310#comment-14290310 ] Tim Allison commented on TIKA-1521: --- I'm getting the test failure on Windows with Java 1.

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290304#comment-14290304 ] Tim Allison commented on TIKA-1529: --- Thank you, [~thetaphi]! > Turn forbidden-apis back

[jira] [Commented] (TIKA-1511) Create a parser for SQLite3

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290303#comment-14290303 ] Tim Allison commented on TIKA-1511: --- I'm not sure I understand the need for that. Won't

Re: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Mattmann, Chris A (3980)
woot thanks dude ++ 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-527 Email: chris.a.mattm...@nasa

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
Works fine here! After I removed the manual override of the plugin lifecycle settings, restart, & maven update, TIKA built successfully. So the setting in Parent POM is enough. I will update the forbidden-apis documentation to help others, too. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Uwe Schindler (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290093#comment-14290093 ] Uwe Schindler commented on TIKA-1529: - Hi, I can confirm, the patch works here. Eclipse

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289962#comment-14289962 ] Hudson commented on TIKA-1529: -- UNSTABLE: Integrated in tika-trunk-jdk1.6 #434 (See [https://

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289932#comment-14289932 ] Hudson commented on TIKA-1529: -- UNSTABLE: Integrated in tika-trunk-jdk1.7 #449 (See [https://

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
Hi Timothy, Your commit looks fine. Basically, this section is just containing some "fake" plugin that is never actively executed, but used by Eclipse to detect which plugins map to internal lifecycles of the Eclipse IDE. It uses this to map for example how to execute the "compile" maven plugi

[jira] [Commented] (TIKA-1511) Create a parser for SQLite3

2015-01-23 Thread Luis Filipe Nassif (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289863#comment-14289863 ] Luis Filipe Nassif commented on TIKA-1511: -- [~talli...@apache.org], is it possible

[jira] [Resolved] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-1529. --- Resolution: Fixed Fixes made in r1654351. Let me know if there are any surprises. > Turn forbidden-ap

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Allison, Timothy B.
Uwe, To confirm, we need to add this ... fully as it is in the parent pom.xml, we should not put the plugin under our regular plugins (which no longer have ? -Original Message- From: Uwe Schindler [mailto:u...@thetaphi.de] Sent: Friday, January 23, 2015 11:47 AM To: dev@tika.apache.o

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Allison, Timothy B.
Will do. -Original Message- From: Mattmann, Chris A (3980) [mailto:chris.a.mattm...@jpl.nasa.gov] Sent: Friday, January 23, 2015 2:11 PM To: dev@tika.apache.org Subject: Re: Forbidden-APIS no longer ran because of carzy POM change awesome. Thanks Uwe. Tim you want to put that in, or you

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
I will add this to the documentation page of forbidden-apis. This may also help Elasticsearch and other people :-) Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Mattmann, Chris A (3980) [mailto:

Re: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Mattmann, Chris A (3980)
awesome. Thanks Uwe. Tim you want to put that in, or you want me to? ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 16

[jira] [Commented] (TIKA-1521) Handle password protected 7zip files

2015-01-23 Thread Nick Burch (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289605#comment-14289605 ] Nick Burch commented on TIKA-1521: -- All unit tests (including that one) pass just fine on

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
Hi, I did further investigation. I had the plugin disabled in my eclipse (you can do this in quick fix for the whole workspace). In fact, if you remove the disable thing, it fails also in Eclipse Luna. If we want to make the plugin automatically "hidden" to all Eclipse versions through our own

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
Hi, this may also help, it also brings the needed information: https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html In fact the problem is: Eclipse has no idea how this plugin should be executed internally in Eclipse. But as this is just a "check plugin" that does not affect

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Konstantin Gribov (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289460#comment-14289460 ] Konstantin Gribov commented on TIKA-1529: - {{new String(bytes, Charset)}} will alwa

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289449#comment-14289449 ] Tim Allison commented on TIKA-1529: --- Agreed on US-ASCII, but aren't there illegal combina

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Uwe Schindler (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289438#comment-14289438 ] Uwe Schindler commented on TIKA-1529: - If you just check for ASCII chars in some string

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Konstantin Gribov (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289429#comment-14289429 ] Konstantin Gribov commented on TIKA-1529: - [~talli...@mitre.org], it works with {{I

[jira] [Commented] (TIKA-1526) ExternalParser should trap/ignore/workarround JDK-8047340 & JDK-8055301 so Turkish Tika users can still use non-external parsers

2015-01-23 Thread Tyler Palsulich (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289419#comment-14289419 ] Tyler Palsulich commented on TIKA-1526: --- This is exactly how I saw the bug. I was con

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289410#comment-14289410 ] Tim Allison commented on TIKA-1529: --- Great! I'm still making mods and creating a static

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289412#comment-14289412 ] Hudson commented on TIKA-1529: -- UNSTABLE: Integrated in tika-trunk-jdk1.7 #448 (See [https://

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tyler Palsulich (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289405#comment-14289405 ] Tyler Palsulich commented on TIKA-1529: --- +1 to {{RuntimeException}}. > Turn forbidde

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tyler Palsulich (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289402#comment-14289402 ] Tyler Palsulich commented on TIKA-1529: --- Yes, Locale.ROOT is OK. > Turn forbidden-ap

Re: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Mattmann, Chris A (3980)
Thanks Uwe, no problem we’ll figure it out. We’ll get it re-enabled and also figure out the Eclipse thing. Thanks for bringing this up! ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Chris A. Mattmann (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289390#comment-14289390 ] Chris A. Mattmann commented on TIKA-1529: - Hi Tim, I tried Uwe's patch on the lates

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
Hi, > There're several places where forbiddenapis will give errors in Tika. > I don't know if there is better way to fallback. E.g. in one of chm parser > classes: > > try { > dle.setName(new String(bytes, "UTF-8")); catch > (UnsupportedCharsetException e) { > dle.setName(new String(bytes));

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289369#comment-14289369 ] Tim Allison commented on TIKA-1529: --- [~grossws], for the following in {noformat}testExtra

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
Hi, > Hmm, weird, that’s a commit from September 2014, Uwe, so quite a while > ago. > > I think I was having some issues in Eclipse complaining about that plugin, so > I > used the workaround presented on StackOverflow to deal with it. > > I’m not fine reverting the commit unless the behavior t

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289362#comment-14289362 ] Tim Allison commented on TIKA-1529: --- Makes sense. I'll try to fix the causes for failure

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Chris A. Mattmann (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289361#comment-14289361 ] Chris A. Mattmann commented on TIKA-1529: - Tim, I'm OK with figuring out how to tur

Re: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Mattmann, Chris A (3980)
Hi Uwe, Thanks. I will check it out. Like I said, I’m not OK reverting anything if my Eclipse keeps complaining at me so we’ll need a fix that handles both. Let me try with the latest version of Eclipse and m2e and see if (with your patch) the issue goes away. Cheers, Chris +

Re: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Mattmann, Chris A (3980)
Hmm, weird, that’s a commit from September 2014, Uwe, so quite a while ago. I think I was having some issues in Eclipse complaining about that plugin, so I used the workaround presented on StackOverflow to deal with it. I’m not fine reverting the commit unless the behavior that it did was preser

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289337#comment-14289337 ] Hudson commented on TIKA-1529: -- UNSTABLE: Integrated in tika-trunk-jdk1.6 #433 (See [https://

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Konstantin Gribov (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289333#comment-14289333 ] Konstantin Gribov commented on TIKA-1529: - I vote for throwing {{RuntimeException}}

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289311#comment-14289311 ] Tim Allison commented on TIKA-1529: --- For UnsupportedEncodingException, Lucene/Solr handle

[jira] [Updated] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison updated TIKA-1529: -- Description: [~thetaphi] recently noticed that forbidden-apis was turned off in r1624185, and he submitte

[jira] [Commented] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289304#comment-14289304 ] Tim Allison commented on TIKA-1529: --- I just fixed issues BasicContentHandlerFactoryTest i

[jira] [Comment Edited] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289304#comment-14289304 ] Tim Allison edited comment on TIKA-1529 at 1/23/15 2:41 PM: I f

[jira] [Created] (TIKA-1529) Turn forbidden-apis back on

2015-01-23 Thread Tim Allison (JIRA)
Tim Allison created TIKA-1529: - Summary: Turn forbidden-apis back on Key: TIKA-1529 URL: https://issues.apache.org/jira/browse/TIKA-1529 Project: Tika Issue Type: Bug Reporter: Tim Al

Re: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Konstantin Gribov
Hi, Uwe. There're several places where forbiddenapis will give errors in Tika. I don't know if there is better way to fallback. E.g. in one of chm parser classes: try { dle.setName(new String(bytes, "UTF-8")); catch (UnsupportedCharsetException e) { dle.setName(new String(bytes)); } Can you

[jira] [Commented] (TIKA-1511) Create a parser for SQLite3

2015-01-23 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289249#comment-14289249 ] Tim Allison commented on TIKA-1511: --- [~gagravarr], in response to your request on TIKA-15

[jira] [Comment Edited] (TIKA-1526) ExternalParser should trap/ignore/workarround JDK-8047340 & JDK-8055301 so Turkish Tika users can still use non-external parsers

2015-01-23 Thread Uwe Schindler (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289182#comment-14289182 ] Uwe Schindler edited comment on TIKA-1526 at 1/23/15 12:32 PM: --

[jira] [Commented] (TIKA-1526) ExternalParser should trap/ignore/workarround JDK-8047340 & JDK-8055301 so Turkish Tika users can still use non-external parsers

2015-01-23 Thread Uwe Schindler (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289182#comment-14289182 ] Uwe Schindler commented on TIKA-1526: - To work around this bug you can in fact do this.

[jira] [Comment Edited] (TIKA-1526) ExternalParser should trap/ignore/workarround JDK-8047340 & JDK-8055301 so Turkish Tika users can still use non-external parsers

2015-01-23 Thread Konstantin Gribov (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289172#comment-14289172 ] Konstantin Gribov edited comment on TIKA-1526 at 1/23/15 12:24 PM: --

[jira] [Commented] (TIKA-1526) ExternalParser should trap/ignore/workarround JDK-8047340 & JDK-8055301 so Turkish Tika users can still use non-external parsers

2015-01-23 Thread Konstantin Gribov (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289172#comment-14289172 ] Konstantin Gribov commented on TIKA-1526: - [~thetaphi], I understand that this is j

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
Here is the patch, mailing list swallowed it: Index: tika-parent/pom.xml === --- tika-parent/pom.xml (revision 1654171) +++ tika-parent/pom.xml (working copy) @@ -274,7 +274,6 @@ - maven-comp

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
The attached patch reverts the change and updates the forbidden plugin. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Uwe Schindler [mailto:u...@thetaphi.de] > Sent: Friday, January 23, 2015 1:00

RE: Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
Here ist he explanation why the plugin is no longer called because of this: - Works for me too, but can anyone explain why? – Andrew Swan May 15 '13 at 6:26 - @Andrew I think this works because m2e is not looking for plugins in pluginManagement, but only in build/plugins. In the

[jira] [Commented] (TIKA-1526) ExternalParser should trap/ignore/workarround JDK-8047340 & JDK-8055301 so Turkish Tika users can still use non-external parsers

2015-01-23 Thread Uwe Schindler (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289125#comment-14289125 ] Uwe Schindler commented on TIKA-1526: - [~grossws]: This bug is not in Maven itsself, th

Forbidden-APIS no longer ran because of carzy POM change

2015-01-23 Thread Uwe Schindler
Hi, I just noticed while checking the problems around the ExternalParsers that the TIKA's build no longer runs the forbidden-apis Maven plugin, so we got a few new violation especially regarding the toUpper/LowerCase(). In fact the following commit broke this: Revision: 1624185 Author: mattman

[jira] [Commented] (TIKA-1526) ExternalParser should trap/ignore/workarround JDK-8047340 & JDK-8055301 so Turkish Tika users can still use non-external parsers

2015-01-23 Thread Konstantin Gribov (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288977#comment-14288977 ] Konstantin Gribov commented on TIKA-1526: - [~thetaphi], they fixed this in 2.0 RC s

[jira] [Commented] (TIKA-1526) ExternalParser should trap/ignore/workarround JDK-8047340 & JDK-8055301 so Turkish Tika users can still use non-external parsers

2015-01-23 Thread Uwe Schindler (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288963#comment-14288963 ] Uwe Schindler commented on TIKA-1526: - I tried it with maven, but this is all too funny