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

Tim Allison commented on TIKA-1325:
-----------------------------------

Happy to do so.  I can't get a clean build, though because of something going 
on in tika bundle:
{noformat}
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.tika.bundle.BundleIT
54 [main] INFO org.ops4j.pax.exam.spi.DefaultExamSystem - Pax Exam System 
(Version: 2.2.0) created.
Jun 09, 2014 11:56:56 AM org.ops4j.pax.url.mvn.internal.AetherBasedResolver 
resolve
INFO: Resolved (org.junit:com.springsource.org.junit:jar:4.4.0) as 
.....m2/repository/org/junit/com.springsource.org.junit/4.4.0/com.springsource.org.junit-4.4.0.jar
ERROR: Bundle org.apache.tika.bundle [7] Error starting 
file:.../tika-bundle/target/test-bundles/tika-bundle.jar 
(org.osgi.framework.BundleException: Unresolved constraint in bundle 
org.apache.tika.bundle [7]: Unable to resolve 7.0: missing requirement [7.0] 
osgi.wiring.package; (osgi.wiring.package=net.jcip.annotations))
org.osgi.framework.BundleException: Unresolved constraint in bundle 
org.apache.tika.bundle [7]: Unable to resolve 7.0: missing requirement [7.0] 
osgi.wiring.package; (osgi.wiring.package=net.jcip.annotations)
        at 
org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3818)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)
        at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)
        at 
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)
        at java.lang.Thread.run(Thread.java:724)
1445 [main] ERROR org.ops4j.pax.exam.junit.JUnit4TestRunner - Exception
org.ops4j.pax.exam.TestContainerException: 
java.lang.reflect.InvocationTargetException
        at 
org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.injectContextAndInvoke(ProbeInvokerImpl.java:118)
        at 
org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.findAndInvoke(ProbeInvokerImpl.java:71)
        at 
org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.call(ProbeInvokerImpl.java:58)
        at 
org.ops4j.pax.exam.nat.internal.NativeTestContainer.call(NativeTestContainer.java:83)
        at 
org.ops4j.pax.exam.spi.reactors.EagerSingleStagedReactor.invoke(EagerSingleStagedReactor.java:85)
        at 
org.ops4j.pax.exam.junit.JUnit4TestRunner$2.evaluate(JUnit4TestRunner.java:259)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
        at 
org.ops4j.pax.exam.junit.JUnit4TestRunner.run(JUnit4TestRunner.java:86)
        at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
        at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
        at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
        at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
        at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at 
org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.injectContextAndInvoke(ProbeInvokerImpl.java:112)
        ... 27 more
Caused by: java.lang.AssertionError: Bundle not activated expected:<32> but 
was:<2>
        at org.junit.Assert.fail(Assert.java:74)
        at org.junit.Assert.failNotEquals(Assert.java:448)
        at org.junit.Assert.assertEquals(Assert.java:102)
        at org.junit.Assert.assertEquals(Assert.java:323)
        at org.apache.tika.bundle.BundleIT.testBundleLoaded(BundleIT.java:78)
        ... 32 more
Tests run: 6, Failures: 1, Errors: 0, Skipped: 3, Time elapsed: 1.776 sec <<< 
FAILURE!
{noformat}

> Move the font metadata definitions to properties
> ------------------------------------------------
>
>                 Key: TIKA-1325
>                 URL: https://issues.apache.org/jira/browse/TIKA-1325
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata, parser
>    Affects Versions: 1.5, 1.6
>            Reporter: Nick Burch
>         Attachments: TIKA-1325_TimeZone.patch
>
>
> As noticed while working on TIKA-1182, the AFM font parser has a bunch of 
> hard coded strings it uses as metadata keys, while the TTF font parser 
> doesn't have many
> We should switch these to being proper Properties, with definitions from a 
> well known standard (+ compatibility fallbacks), and have both use largely 
> the same set



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to