tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-2710) Set Tika to OSGi Execution Environment JavaSE-1.8
Date Sat, 18 Aug 2018 03:11:00 GMT

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

Hudson commented on TIKA-2710:
------------------------------

SUCCESS: Integrated in Jenkins build tika-branch-1x #78 (See [https://builds.apache.org/job/tika-branch-1x/78/])
TIKA-2710 - Change Tika OSGi Execution Environment to 1.8. (bob: [https://github.com/apache/tika/commit/1f5669dcd6a00f2591122cb6f4cd55b806b1676f])
* (edit) tika-bundle/pom.xml
* (add) tika-bundle/src/main/resources/META-INF/MANIFEST.MF
TIKA-2710 - Change Tika OSGi Execution Environment to 1.8.  Format fix. (bob: [https://github.com/apache/tika/commit/3c76b3ae0c700b29f8adff2b18bebc81272dfee4])
* (edit) tika-bundle/pom.xml


> Set Tika to OSGi Execution Environment JavaSE-1.8
> -------------------------------------------------
>
>                 Key: TIKA-2710
>                 URL: https://issues.apache.org/jira/browse/TIKA-2710
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Bob Paulin
>            Assignee: Bob Paulin
>            Priority: Major
>
> In TIKA-2692 the OSGi execution environment (osgi.ee) was removed since it was coming
out as 9.0 when 1.8 was expected.  This is due to the org.ow2.asm:asm:6.2 JAR file having
a module-info.class within it.  Turns out this causes the maven-bundle-plugin to increase
the execution environment to Java 9.  Rather than removing osgi.ee we should manually set
it to 1.8 which is correct since Java 8 will simply ignore the module-info.class.  This can
be reverted once Tika moves up to Java 9 or beyond.{{}}



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

Mime
View raw message