[jira] [Updated] (TIKA-2382) Remove innerText of

[Jayesh Shende (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TIKA-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh Shende updated TIKA-2382:

Description: If HTML page contains 

[jira] [Created] (TIKA-2382) Remove innerText of

[Jayesh Shende (JIRA)]

Jayesh Shende created TIKA-2382:
---

 Summary: Remove innerText of 

[jira] [Resolved] (TIKA-2379) tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not exists

[Bob Paulin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TIKA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bob Paulin resolved TIKA-2379.
--
Resolution: Fixed

> tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not 
> exists
> --
>
> Key: TIKA-2379
> URL: https://issues.apache.org/jira/browse/TIKA-2379
> Project: Tika
>  Issue Type: Bug
>Affects Versions: 1.15
>Reporter: Claus Ibsen
>Assignee: Bob Paulin
>Priority: Blocker
>
> The new release 1.15 now fails in Apache Camel when we run our OSGi tests
> {code}
> test(org.apache.camel.itest.karaf.CamelTikaTest)  Time elapsed: 7.212 sec  
> <<< ERROR!
> org.ops4j.pax.exam.WrappedTestContainerException: 
> [test(org.apache.camel.itest.karaf.CamelTikaTest): Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-tika; 
> type=karaf.feature; version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; 
> filter:="(&(osgi.identity=camel-tika)(type=karaf.feature)(version>=2.20.0.SNAPSHOT)(version<=2.20.0.SNAPSHOT))"
>  [caused by: Unable to resolve camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [camel-tika/2.20.0.SNAPSHOT] osgi.identity; 
> osgi.identity=org.apache.camel.camel-tika; type=osgi.bundle; 
> version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; resolution:=mandatory [caused 
> by: Unable to resolve org.apache.camel.camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [org.apache.camel.camel-tika/2.20.0.SNAPSHOT] 
> osgi.wiring.package; 
> filter:="(osgi.wiring.package=org.apache.tika.parser.html)" [caused by: 
> Unable to resolve org.apache.tika.bundle/1.15.0: missing requirement 
> [org.apache.tika.bundle/1.15.0] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.slf4j.event)(version>=1.7.0)(!(version>=2.0.0)))"
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
>   at 
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:347)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that tika-bundle has an import on package
> {code}
> org.slf4j.event;version="[1.7,2)"
> {code}
> And that package does not exists in 1.7.x. It looks like its a new thing that 
> comes in slf4j 1.8 onwards but they have only alpha releases
> http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.slf4j.event%22
> It would be good to get this fixed. I wonder if that event package is really 
> needed? And if not then please remove that import in the OSGi manifest file.
> Otherwise you would need to depend on slf4j-api version 1.8 which is still 
> not released in GA and not widely in use. I would suggest to be compatible 
> with slfj4 1.7 so the Tika upgrade from eg 1.14 to 1.15 is a smooth upgrade 
> for end users.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TIKA-2379) tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not exists

[Bob Paulin (JIRA)]

[ 
https://issues.apache.org/jira/browse/TIKA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032423#comment-16032423
 ] 

Bob Paulin commented on TIKA-2379:
--

Looks like a lot changed in this bundle between 1.14.  I couldn't find any 
JIRAs or detailed commit comments to backup these modifications so I did revert 
many of them.  Here's the highlights:
* Changed SLF4J's resolution to be  optional again.  This should fix 
[~davsclaus] issue.
* Removed Dynamic-Import statement.  I don't believe this is appropriate.
* Added Pax Logging bundles to the test as some of the Parsers do require 
org.apache.commons.logging to run.
* Upgraded the OSGi spec, Felix runtime, and Pax Exam for the test runner.

Please review.

> tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not 
> exists
> --
>
> Key: TIKA-2379
> URL: https://issues.apache.org/jira/browse/TIKA-2379
> Project: Tika
>  Issue Type: Bug
>Affects Versions: 1.15
>Reporter: Claus Ibsen
>Assignee: Bob Paulin
>Priority: Blocker
>
> The new release 1.15 now fails in Apache Camel when we run our OSGi tests
> {code}
> test(org.apache.camel.itest.karaf.CamelTikaTest)  Time elapsed: 7.212 sec  
> <<< ERROR!
> org.ops4j.pax.exam.WrappedTestContainerException: 
> [test(org.apache.camel.itest.karaf.CamelTikaTest): Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-tika; 
> type=karaf.feature; version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; 
> filter:="(&(osgi.identity=camel-tika)(type=karaf.feature)(version>=2.20.0.SNAPSHOT)(version<=2.20.0.SNAPSHOT))"
>  [caused by: Unable to resolve camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [camel-tika/2.20.0.SNAPSHOT] osgi.identity; 
> osgi.identity=org.apache.camel.camel-tika; type=osgi.bundle; 
> version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; resolution:=mandatory [caused 
> by: Unable to resolve org.apache.camel.camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [org.apache.camel.camel-tika/2.20.0.SNAPSHOT] 
> osgi.wiring.package; 
> filter:="(osgi.wiring.package=org.apache.tika.parser.html)" [caused by: 
> Unable to resolve org.apache.tika.bundle/1.15.0: missing requirement 
> [org.apache.tika.bundle/1.15.0] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.slf4j.event)(version>=1.7.0)(!(version>=2.0.0)))"
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
>   at 
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:347)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that tika-bundle has an import on package
> {code}
> org.slf4j.event;version="[1.7,2)"
> {code}
> And that package does not exists in 1.7.x. It looks like its a new thing that 
> comes in slf4j 1.8 onwards but they have only alpha releases
> http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.slf4j.event%22
> It would be good to get this fixed. I wonder if that event package is really 
> needed? And if not then please remove that import in the OSGi manifest file.
> Otherwise you would need to depend on slf4j-api version 1.8 which is still 
> not released in GA and not widely in use. I would suggest to be compatible 
> with slfj4 1.7 so the Tika upgrade from eg 1.14 to 1.15 is a smooth upgrade 
> for end users.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TIKA-2379) tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not exists

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/TIKA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032420#comment-16032420
 ] 

Hudson commented on TIKA-2379:
--

FAILURE: Integrated in Jenkins build Tika-trunk #1281 (See 
[https://builds.apache.org/job/Tika-trunk/1281/])
TIKA-2379 - Make logging in bundle optional.  Fix test. (bob: 
[https://github.com/apache/tika/commit/fa1d41101f839692cc997c8933eeb6045d7dc484])
* (edit) tika-bundle/pom.xml
* (edit) tika-bundle/src/test/java/org/apache/tika/bundle/BundleIT.java
* (delete) tika-bundle/src/test/resources/exam.properties
TIKA-2379 - Add test scope back in for JUnit. (bob: 
[https://github.com/apache/tika/commit/c3cf30fa7de70b350b6344459cbb39410f24d438])
* (edit) tika-bundle/pom.xml


> tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not 
> exists
> --
>
> Key: TIKA-2379
> URL: https://issues.apache.org/jira/browse/TIKA-2379
> Project: Tika
>  Issue Type: Bug
>Affects Versions: 1.15
>Reporter: Claus Ibsen
>Assignee: Bob Paulin
>Priority: Blocker
>
> The new release 1.15 now fails in Apache Camel when we run our OSGi tests
> {code}
> test(org.apache.camel.itest.karaf.CamelTikaTest)  Time elapsed: 7.212 sec  
> <<< ERROR!
> org.ops4j.pax.exam.WrappedTestContainerException: 
> [test(org.apache.camel.itest.karaf.CamelTikaTest): Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-tika; 
> type=karaf.feature; version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; 
> filter:="(&(osgi.identity=camel-tika)(type=karaf.feature)(version>=2.20.0.SNAPSHOT)(version<=2.20.0.SNAPSHOT))"
>  [caused by: Unable to resolve camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [camel-tika/2.20.0.SNAPSHOT] osgi.identity; 
> osgi.identity=org.apache.camel.camel-tika; type=osgi.bundle; 
> version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; resolution:=mandatory [caused 
> by: Unable to resolve org.apache.camel.camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [org.apache.camel.camel-tika/2.20.0.SNAPSHOT] 
> osgi.wiring.package; 
> filter:="(osgi.wiring.package=org.apache.tika.parser.html)" [caused by: 
> Unable to resolve org.apache.tika.bundle/1.15.0: missing requirement 
> [org.apache.tika.bundle/1.15.0] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.slf4j.event)(version>=1.7.0)(!(version>=2.0.0)))"
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
>   at 
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:347)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that tika-bundle has an import on package
> {code}
> org.slf4j.event;version="[1.7,2)"
> {code}
> And that package does not exists in 1.7.x. It looks like its a new thing that 
> comes in slf4j 1.8 onwards but they have only alpha releases
> http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.slf4j.event%22
> It would be good to get this fixed. I wonder if that event package is really 
> needed? And if not then please remove that import in the OSGi manifest file.
> Otherwise you would need to depend on slf4j-api version 1.8 which is still 
> not released in GA and not widely in use. I would suggest to be compatible 
> with slfj4 1.7 so the Tika upgrade from eg 1.14 to 1.15 is a smooth upgrade 
> for end users.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: experiences with Tika in Docker

[Thejan Wijesinghe]

Hi Tim,

I've used Tika -server in docker but as a single instance only. Yes, its
ability to limit container's resources with related to memory & CPU in the
host machine is great, it gives us so much flexibility, we could enforce
hard/soft memory limits, we could even manipulate the host machine's CPU
cycles. Yes, it also limits risks of executing arbitrary code & XXE
vulnerabilities. I already asked Prof. Chris Mattmann about officially
moving to dockerhub. He said I need to make a mail to apache infra asking
about this. Unfortunately, I still couldn't find a time to make that mail.

We already have multiple dockerfiles in Tika, , dockerfile in tika-server,
InceptionRestDockerfile, InceptionVideoRestDockerfile,
Im2txtRestDockerfile(PR #180-for image captioning).

Part of my GSoC project is to unify the existing REST services such as
object recognition, image captioning. My idea is to unify all of those REST
services where the user can start/terminate, see statistics of any REST
service through a web based GUI. I'm expecting to use a fusion of nginx(as
the reverse proxy server) & docker to make it work. So obviously we will
see docker much often in Tika.

+1 for your thought to looking into hardening the tika-server with the help
of docker.

best,
ThejanW

On Thu, Jun 1, 2017 at 1:03 AM, Allison, Timothy B. 
wrote:

> Dave Meikle, Tom and All,
>
> How many of us are using Tika in Docker?  If so, how exactly are you
> using it?  Single instance, swarm, Kubernetes, something else?  People fear
> I/O hit with tika-server...what are your experiences?
> I really like the ability to limit the number of CPUs in the Docker
> container.  If a single doc causes multithreaded gc to go nuts, that won't
> kill an entire machine.  This also cleanly limits the risk from XXE or
> arbitrary code execution, right?
>
> If this is one of the ways of the future for big data, we might want to
> look into hardening tika-server (OOMs, timeouts).  What do you all think?
>
> Cheers,
>
> Tim
>
> Timothy B. Allison, Ph.D.
> Principal Artificial Intelligence Engineer
> Group Lead
> K83E/Human Language Technology
> The MITRE Corporation
> 7515 Colshire Drive, McLean, VA  22102
> 703-983-2473 (phone); 703-983-1379 (fax)
>
>

[jira] [Resolved] (TIKA-2381) Include tika-eval artifact in release

[Tim Allison (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TIKA-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Allison resolved TIKA-2381.
---
Resolution: Duplicate

> Include tika-eval artifact in release
> -
>
> Key: TIKA-2381
> URL: https://issues.apache.org/jira/browse/TIKA-2381
> Project: Tika
>  Issue Type: Improvement
>Reporter: Tim Allison
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (TIKA-2381) Include tika-eval artifact in release

[Tim Allison (JIRA)]

Tim Allison created TIKA-2381:
-

 Summary: Include tika-eval artifact in release
 Key: TIKA-2381
 URL: https://issues.apache.org/jira/browse/TIKA-2381
 Project: Tika
  Issue Type: Improvement
Reporter: Tim Allison






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

experiences with Tika in Docker

[Allison, Timothy B.]

Dave Meikle, Tom and All,

How many of us are using Tika in Docker?  If so, how exactly are you using 
it?  Single instance, swarm, Kubernetes, something else?  People fear I/O hit 
with tika-server...what are your experiences?
I really like the ability to limit the number of CPUs in the Docker container.  
If a single doc causes multithreaded gc to go nuts, that won't kill an entire 
machine.  This also cleanly limits the risk from XXE or arbitrary code 
execution, right?

If this is one of the ways of the future for big data, we might want to look 
into hardening tika-server (OOMs, timeouts).  What do you all think?

Cheers,

Tim

Timothy B. Allison, Ph.D.
Principal Artificial Intelligence Engineer
Group Lead
K83E/Human Language Technology
The MITRE Corporation
7515 Colshire Drive, McLean, VA  22102
703-983-2473 (phone); 703-983-1379 (fax)

[jira] [Created] (TIKA-2380) Upgrade to Jackcess 2.1.8 when available

[Tim Allison (JIRA)]

Tim Allison created TIKA-2380:
-

 Summary: Upgrade to Jackcess 2.1.8 when available
 Key: TIKA-2380
 URL: https://issues.apache.org/jira/browse/TIKA-2380
 Project: Tika
  Issue Type: Improvement
Reporter: Tim Allison






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (TIKA-2378) Error extracting text from application/x-msaccess mime type

[Tim Allison (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TIKA-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Allison updated TIKA-2378:
--
Affects Version/s: 1.15

> Error extracting text from application/x-msaccess mime type
> ---
>
> Key: TIKA-2378
> URL: https://issues.apache.org/jira/browse/TIKA-2378
> Project: Tika
>  Issue Type: Bug
>  Components: parser
>Affects Versions: 1.14, 1.15
>Reporter: Steve Reynolds
>Priority: Minor
> Attachments: Stacktrace.txt, Students.accdb
>
>
> Tika failed to extract text from an MS Access file with mime type = 
> application/x-msaccess
> I will attach an example file and the stacktrace.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TIKA-2379) tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not exists

[Bob Paulin (JIRA)]

[ 
https://issues.apache.org/jira/browse/TIKA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031223#comment-16031223
 ] 

Bob Paulin commented on TIKA-2379:
--

Will take a look.  I'm guessing there was a change in the dependency tree that 
caused this.  We can probably add a PaxExam test with a SLF4J 1.7 bundle to 
ensure this works in future releases.  Thanks for the heads up 
[~talli...@mitre.org]

> tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not 
> exists
> --
>
> Key: TIKA-2379
> URL: https://issues.apache.org/jira/browse/TIKA-2379
> Project: Tika
>  Issue Type: Bug
>Affects Versions: 1.15
>Reporter: Claus Ibsen
>Priority: Blocker
>
> The new release 1.15 now fails in Apache Camel when we run our OSGi tests
> {code}
> test(org.apache.camel.itest.karaf.CamelTikaTest)  Time elapsed: 7.212 sec  
> <<< ERROR!
> org.ops4j.pax.exam.WrappedTestContainerException: 
> [test(org.apache.camel.itest.karaf.CamelTikaTest): Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-tika; 
> type=karaf.feature; version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; 
> filter:="(&(osgi.identity=camel-tika)(type=karaf.feature)(version>=2.20.0.SNAPSHOT)(version<=2.20.0.SNAPSHOT))"
>  [caused by: Unable to resolve camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [camel-tika/2.20.0.SNAPSHOT] osgi.identity; 
> osgi.identity=org.apache.camel.camel-tika; type=osgi.bundle; 
> version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; resolution:=mandatory [caused 
> by: Unable to resolve org.apache.camel.camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [org.apache.camel.camel-tika/2.20.0.SNAPSHOT] 
> osgi.wiring.package; 
> filter:="(osgi.wiring.package=org.apache.tika.parser.html)" [caused by: 
> Unable to resolve org.apache.tika.bundle/1.15.0: missing requirement 
> [org.apache.tika.bundle/1.15.0] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.slf4j.event)(version>=1.7.0)(!(version>=2.0.0)))"
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
>   at 
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:347)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that tika-bundle has an import on package
> {code}
> org.slf4j.event;version="[1.7,2)"
> {code}
> And that package does not exists in 1.7.x. It looks like its a new thing that 
> comes in slf4j 1.8 onwards but they have only alpha releases
> http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.slf4j.event%22
> It would be good to get this fixed. I wonder if that event package is really 
> needed? And if not then please remove that import in the OSGi manifest file.
> Otherwise you would need to depend on slf4j-api version 1.8 which is still 
> not released in GA and not widely in use. I would suggest to be compatible 
> with slfj4 1.7 so the Tika upgrade from eg 1.14 to 1.15 is a smooth upgrade 
> for end users.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (TIKA-2379) tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not exists

[Bob Paulin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TIKA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bob Paulin reassigned TIKA-2379:


Assignee: Bob Paulin

> tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not 
> exists
> --
>
> Key: TIKA-2379
> URL: https://issues.apache.org/jira/browse/TIKA-2379
> Project: Tika
>  Issue Type: Bug
>Affects Versions: 1.15
>Reporter: Claus Ibsen
>Assignee: Bob Paulin
>Priority: Blocker
>
> The new release 1.15 now fails in Apache Camel when we run our OSGi tests
> {code}
> test(org.apache.camel.itest.karaf.CamelTikaTest)  Time elapsed: 7.212 sec  
> <<< ERROR!
> org.ops4j.pax.exam.WrappedTestContainerException: 
> [test(org.apache.camel.itest.karaf.CamelTikaTest): Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-tika; 
> type=karaf.feature; version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; 
> filter:="(&(osgi.identity=camel-tika)(type=karaf.feature)(version>=2.20.0.SNAPSHOT)(version<=2.20.0.SNAPSHOT))"
>  [caused by: Unable to resolve camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [camel-tika/2.20.0.SNAPSHOT] osgi.identity; 
> osgi.identity=org.apache.camel.camel-tika; type=osgi.bundle; 
> version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; resolution:=mandatory [caused 
> by: Unable to resolve org.apache.camel.camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [org.apache.camel.camel-tika/2.20.0.SNAPSHOT] 
> osgi.wiring.package; 
> filter:="(osgi.wiring.package=org.apache.tika.parser.html)" [caused by: 
> Unable to resolve org.apache.tika.bundle/1.15.0: missing requirement 
> [org.apache.tika.bundle/1.15.0] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.slf4j.event)(version>=1.7.0)(!(version>=2.0.0)))"
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
>   at 
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:347)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that tika-bundle has an import on package
> {code}
> org.slf4j.event;version="[1.7,2)"
> {code}
> And that package does not exists in 1.7.x. It looks like its a new thing that 
> comes in slf4j 1.8 onwards but they have only alpha releases
> http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.slf4j.event%22
> It would be good to get this fixed. I wonder if that event package is really 
> needed? And if not then please remove that import in the OSGi manifest file.
> Otherwise you would need to depend on slf4j-api version 1.8 which is still 
> not released in GA and not widely in use. I would suggest to be compatible 
> with slfj4 1.7 so the Tika upgrade from eg 1.14 to 1.15 is a smooth upgrade 
> for end users.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TIKA-2378) Error extracting text from application/x-msaccess mime type

[Steve Reynolds (JIRA)]

[ 
https://issues.apache.org/jira/browse/TIKA-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031217#comment-16031217
 ] 

Steve Reynolds commented on TIKA-2378:
--

Jackcess Bug has been fixed in trunk and will be in the 2.1.8 release.
See: https://sourceforge.net/p/jackcess/bugs/142/


> Error extracting text from application/x-msaccess mime type
> ---
>
> Key: TIKA-2378
> URL: https://issues.apache.org/jira/browse/TIKA-2378
> Project: Tika
>  Issue Type: Bug
>  Components: parser
>Affects Versions: 1.14
>Reporter: Steve Reynolds
>Priority: Minor
> Attachments: Stacktrace.txt, Students.accdb
>
>
> Tika failed to extract text from an MS Access file with mime type = 
> application/x-msaccess
> I will attach an example file and the stacktrace.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (TIKA-1804) Tika use no free json.org

[Tim Allison (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TIKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Allison updated TIKA-1804:
--
Priority: Blocker  (was: Major)

> 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 cattaneo
>Priority: Blocker
>
> Hi
> Your project is licensed under Apache License Version 2,
> but your code pulls in code from json.org under Douglas Crockford’s bad 
> licence [1] , and is non-free [2].
> Such usage restriction makes the license incompatible with The Open Source 
> Definition and
> The Free Software Definition. Because Tika binary distribution includes this 
> software,
> it effectively becomes proprietary software itself.
> You may also comment that the json.org license is valid for You but for many 
> Linux distributions it is not acceptable.
> I hope to continue to maintain Tika for Fedora, without having to run into 
> these problems.
> Please try to replace it with one of the many free alternatives.
> Regards
> [1]
> ./tika-1.11/tika-parsers/src/main/java/org/apache/tika/parser/journal/GrobidRESTParser.java
> ./tika-1.11/tika-parsers/src/main/java/org/apache/tika/parser/journal/JournalParser.java
> ./tika-1.11/tika-parsers/src/main/java/org/apache/tika/parser/journal/TEIParser.java
> [2]
> https://wiki.debian.org/qa.debian.org/jsonevil
> http://www.sonatype.com/people/2012/03/use-json-well-youd-better-not-be-evil/
> http://tanguy.ortolo.eu/blog/article46/json-license



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TIKA-2379) tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not exists

[Tim Allison (JIRA)]

[ 
https://issues.apache.org/jira/browse/TIKA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031091#comment-16031091
 ] 

Tim Allison commented on TIKA-2379:
---

[~cib...@e-ma.net], thank you for opening this.

[~bobpaulin], how can we make sure this never happens again?

Looks like 1.15 is actually 1.16-rc1? :(


> tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not 
> exists
> --
>
> Key: TIKA-2379
> URL: https://issues.apache.org/jira/browse/TIKA-2379
> Project: Tika
>  Issue Type: Bug
>Affects Versions: 1.15
>Reporter: Claus Ibsen
>Priority: Blocker
>
> The new release 1.15 now fails in Apache Camel when we run our OSGi tests
> {code}
> test(org.apache.camel.itest.karaf.CamelTikaTest)  Time elapsed: 7.212 sec  
> <<< ERROR!
> org.ops4j.pax.exam.WrappedTestContainerException: 
> [test(org.apache.camel.itest.karaf.CamelTikaTest): Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-tika; 
> type=karaf.feature; version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; 
> filter:="(&(osgi.identity=camel-tika)(type=karaf.feature)(version>=2.20.0.SNAPSHOT)(version<=2.20.0.SNAPSHOT))"
>  [caused by: Unable to resolve camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [camel-tika/2.20.0.SNAPSHOT] osgi.identity; 
> osgi.identity=org.apache.camel.camel-tika; type=osgi.bundle; 
> version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; resolution:=mandatory [caused 
> by: Unable to resolve org.apache.camel.camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [org.apache.camel.camel-tika/2.20.0.SNAPSHOT] 
> osgi.wiring.package; 
> filter:="(osgi.wiring.package=org.apache.tika.parser.html)" [caused by: 
> Unable to resolve org.apache.tika.bundle/1.15.0: missing requirement 
> [org.apache.tika.bundle/1.15.0] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.slf4j.event)(version>=1.7.0)(!(version>=2.0.0)))"
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
>   at 
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:347)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that tika-bundle has an import on package
> {code}
> org.slf4j.event;version="[1.7,2)"
> {code}
> And that package does not exists in 1.7.x. It looks like its a new thing that 
> comes in slf4j 1.8 onwards but they have only alpha releases
> http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.slf4j.event%22
> It would be good to get this fixed. I wonder if that event package is really 
> needed? And if not then please remove that import in the OSGi manifest file.
> Otherwise you would need to depend on slf4j-api version 1.8 which is still 
> not released in GA and not widely in use. I would suggest to be compatible 
> with slfj4 1.7 so the Tika upgrade from eg 1.14 to 1.15 is a smooth upgrade 
> for end users.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (TIKA-2379) tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not exists

[Tim Allison (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TIKA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Allison updated TIKA-2379:
--
Priority: Blocker  (was: Major)

> tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not 
> exists
> --
>
> Key: TIKA-2379
> URL: https://issues.apache.org/jira/browse/TIKA-2379
> Project: Tika
>  Issue Type: Bug
>Affects Versions: 1.15
>Reporter: Claus Ibsen
>Priority: Blocker
>
> The new release 1.15 now fails in Apache Camel when we run our OSGi tests
> {code}
> test(org.apache.camel.itest.karaf.CamelTikaTest)  Time elapsed: 7.212 sec  
> <<< ERROR!
> org.ops4j.pax.exam.WrappedTestContainerException: 
> [test(org.apache.camel.itest.karaf.CamelTikaTest): Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-tika; 
> type=karaf.feature; version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; 
> filter:="(&(osgi.identity=camel-tika)(type=karaf.feature)(version>=2.20.0.SNAPSHOT)(version<=2.20.0.SNAPSHOT))"
>  [caused by: Unable to resolve camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [camel-tika/2.20.0.SNAPSHOT] osgi.identity; 
> osgi.identity=org.apache.camel.camel-tika; type=osgi.bundle; 
> version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; resolution:=mandatory [caused 
> by: Unable to resolve org.apache.camel.camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [org.apache.camel.camel-tika/2.20.0.SNAPSHOT] 
> osgi.wiring.package; 
> filter:="(osgi.wiring.package=org.apache.tika.parser.html)" [caused by: 
> Unable to resolve org.apache.tika.bundle/1.15.0: missing requirement 
> [org.apache.tika.bundle/1.15.0] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.slf4j.event)(version>=1.7.0)(!(version>=2.0.0)))"
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
>   at 
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:347)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that tika-bundle has an import on package
> {code}
> org.slf4j.event;version="[1.7,2)"
> {code}
> And that package does not exists in 1.7.x. It looks like its a new thing that 
> comes in slf4j 1.8 onwards but they have only alpha releases
> http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.slf4j.event%22
> It would be good to get this fixed. I wonder if that event package is really 
> needed? And if not then please remove that import in the OSGi manifest file.
> Otherwise you would need to depend on slf4j-api version 1.8 which is still 
> not released in GA and not widely in use. I would suggest to be compatible 
> with slfj4 1.7 so the Tika upgrade from eg 1.14 to 1.15 is a smooth upgrade 
> for end users.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (TIKA-2379) tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not exists

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TIKA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated TIKA-2379:
--
Summary: tika-bundle 1.15 has wrong import of org.sfl4j.event package which 
does not exists  (was: tika-bundle 1.1.5 has wrong import of org.sfl4j.event 
package which does not exists)

> tika-bundle 1.15 has wrong import of org.sfl4j.event package which does not 
> exists
> --
>
> Key: TIKA-2379
> URL: https://issues.apache.org/jira/browse/TIKA-2379
> Project: Tika
>  Issue Type: Bug
>Affects Versions: 1.15
>Reporter: Claus Ibsen
>
> The new release 1.15 now fails in Apache Camel when we run our OSGi tests
> {code}
> test(org.apache.camel.itest.karaf.CamelTikaTest)  Time elapsed: 7.212 sec  
> <<< ERROR!
> org.ops4j.pax.exam.WrappedTestContainerException: 
> [test(org.apache.camel.itest.karaf.CamelTikaTest): Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-tika; 
> type=karaf.feature; version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; 
> filter:="(&(osgi.identity=camel-tika)(type=karaf.feature)(version>=2.20.0.SNAPSHOT)(version<=2.20.0.SNAPSHOT))"
>  [caused by: Unable to resolve camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [camel-tika/2.20.0.SNAPSHOT] osgi.identity; 
> osgi.identity=org.apache.camel.camel-tika; type=osgi.bundle; 
> version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; resolution:=mandatory [caused 
> by: Unable to resolve org.apache.camel.camel-tika/2.20.0.SNAPSHOT: missing 
> requirement [org.apache.camel.camel-tika/2.20.0.SNAPSHOT] 
> osgi.wiring.package; 
> filter:="(osgi.wiring.package=org.apache.tika.parser.html)" [caused by: 
> Unable to resolve org.apache.tika.bundle/1.15.0: missing requirement 
> [org.apache.tika.bundle/1.15.0] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.slf4j.event)(version>=1.7.0)(!(version>=2.0.0)))"
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
>   at 
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:347)
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218)
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that tika-bundle has an import on package
> {code}
> org.slf4j.event;version="[1.7,2)"
> {code}
> And that package does not exists in 1.7.x. It looks like its a new thing that 
> comes in slf4j 1.8 onwards but they have only alpha releases
> http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.slf4j.event%22
> It would be good to get this fixed. I wonder if that event package is really 
> needed? And if not then please remove that import in the OSGi manifest file.
> Otherwise you would need to depend on slf4j-api version 1.8 which is still 
> not released in GA and not widely in use. I would suggest to be compatible 
> with slfj4 1.7 so the Tika upgrade from eg 1.14 to 1.15 is a smooth upgrade 
> for end users.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (TIKA-2379) tika-bundle 1.1.5 has wrong import of org.sfl4j.event package which does not exists

[Claus Ibsen (JIRA)]

Claus Ibsen created TIKA-2379:
-

 Summary: tika-bundle 1.1.5 has wrong import of org.sfl4j.event 
package which does not exists
 Key: TIKA-2379
 URL: https://issues.apache.org/jira/browse/TIKA-2379
 Project: Tika
  Issue Type: Bug
Affects Versions: 1.15
Reporter: Claus Ibsen


The new release 1.15 now fails in Apache Camel when we run our OSGi tests
{code}
test(org.apache.camel.itest.karaf.CamelTikaTest)  Time elapsed: 7.212 sec  <<< 
ERROR!
org.ops4j.pax.exam.WrappedTestContainerException: 
[test(org.apache.camel.itest.karaf.CamelTikaTest): Unable to resolve root: 
missing requirement [root] osgi.identity; osgi.identity=camel-tika; 
type=karaf.feature; version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; 
filter:="(&(osgi.identity=camel-tika)(type=karaf.feature)(version>=2.20.0.SNAPSHOT)(version<=2.20.0.SNAPSHOT))"
 [caused by: Unable to resolve camel-tika/2.20.0.SNAPSHOT: missing requirement 
[camel-tika/2.20.0.SNAPSHOT] osgi.identity; 
osgi.identity=org.apache.camel.camel-tika; type=osgi.bundle; 
version="[2.20.0.SNAPSHOT,2.20.0.SNAPSHOT]"; resolution:=mandatory [caused by: 
Unable to resolve org.apache.camel.camel-tika/2.20.0.SNAPSHOT: missing 
requirement [org.apache.camel.camel-tika/2.20.0.SNAPSHOT] osgi.wiring.package; 
filter:="(osgi.wiring.package=org.apache.tika.parser.html)" [caused by: Unable 
to resolve org.apache.tika.bundle/1.15.0: missing requirement 
[org.apache.tika.bundle/1.15.0] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=org.slf4j.event)(version>=1.7.0)(!(version>=2.0.0)))"
at 
org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
at 
org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:347)
at 
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218)
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:285)
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1170)
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1069)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
{code}

The problem is that tika-bundle has an import on package

{code}
org.slf4j.event;version="[1.7,2)"
{code}

And that package does not exists in 1.7.x. It looks like its a new thing that 
comes in slf4j 1.8 onwards but they have only alpha releases
http://search.maven.org/#search%7Cga%7C1%7Cfc%3A%22org.slf4j.event%22

It would be good to get this fixed. I wonder if that event package is really 
needed? And if not then please remove that import in the OSGi manifest file.

Otherwise you would need to depend on slf4j-api version 1.8 which is still not 
released in GA and not widely in use. I would suggest to be compatible with 
slfj4 1.7 so the Tika upgrade from eg 1.14 to 1.15 is a smooth upgrade for end 
users.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)