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-1524) Can install Tika-Bundle, missing JUnit dependency
Date Tue, 28 Jul 2015 13:56:04 GMT

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

Hudson commented on TIKA-1524:

SUCCESS: Integrated in tika-trunk-jdk1.7 #804 (See [https://builds.apache.org/job/tika-trunk-jdk1.7/804/])
Remove junit from OSGi bundle deps

Test dependencies removed from OSGi bundle `Import-Package` manifest header.

Extra integration test by Bob Pailin <bob@apache.org> added to avoid regressions
with junit packages included to inappropriate manifest entries.

Fixes TIKA-1524 (grossws: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1693089)
* /tika/trunk/tika-bundle/pom.xml
* /tika/trunk/tika-bundle/src/test/java/org/apache/tika/bundle/BundleIT.java

> Can install Tika-Bundle, missing JUnit dependency
> -------------------------------------------------
>                 Key: TIKA-1524
>                 URL: https://issues.apache.org/jira/browse/TIKA-1524
>             Project: Tika
>          Issue Type: Bug
>          Components: packaging
>    Affects Versions: 1.7
>         Environment: Karaf 2.3.6
>            Reporter: Niels
>         Attachments: TIKA-1524.patch, TIKA-1524.patch, TIKA-1524.patch, TikaBundleNoJUnit.patch
> When I'm trying to install a feature which has a dependency on the Tika-Bundle, it fails
to install. It indicates it's missing a dependency to JUnit. 
> Momentarily I solved this for myself by reverting back to Tika-Bundle version 1.6
> Error executing command: Could not start bundle mvn:org.apache.tika/tika-bundle/1.7 in
feature(s): Unresolved constraint in bundle org.apache.tika.bundle [336]: Unable to resolve
336.0: missing requirement [336.0] osgi.wiring.package; (osgi.wiring.package=org.junit.internal)

This message was sent by Atlassian JIRA

View raw message