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

Tim Allison edited comment on TIKA-2692 at 7/26/18 6:50 PM:
------------------------------------------------------------

After further general upgrades, I had problems with tika-bundle.  The initial 
exception was that it didn't know what to do with {{module-info.class}}.  

I upgraded {{maven-bundle-plugin}} to 3.5.1, and then there was a problem 
because it was adding:
{{Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=9.0))"}} to 
the Manifest which made the bundle not work with Java 8.

As a temporary work-around, I added {{<_noee>true</_noee>}} to tika-bundle's 
pom.  This works, but...let me know if there are better options.  Help, 
[~bobpaulin]!
 


was (Author: talli...@mitre.org):
After further general upgrades, I had problems with tika-bundle.  The initial 
exception was that it didn't know what to do with {{module-info.java}}.  I 
upgraded {{maven-bundle-plugin}} to 3.5.1, and then there was a problem because 
it was adding:
{{Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=9.0))"}} to 
the Manifest which made the bundle not work with Java 8.

As a temporary work-around, I added {{<_noee>true</_noee>}} to tika-bundle's 
pom.  This works, but...

Let me know if there are better options.  Help, [~bobpaulin]!
 

> Blanket upgrades in prep for 1.19
> ---------------------------------
>
>                 Key: TIKA-2692
>                 URL: https://issues.apache.org/jira/browse/TIKA-2692
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Major
>
> On the dev list [~solomax] recommended using: 
> https://sonatype.github.io/ossindex-maven/maven-plugin/ to identify 
> vulnerable dependencies.
> Let's do that and make other general upgrades as well in prep for 1.19.
> This is a blanket ticket to cover these upgrades.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to