[jira] [Comment Edited] (TIKA-2925) General dependency/plugin upgrades for 1.23

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Comment Edited] (TIKA-2925) General dependency/plugin upgrades for 1.23

David Eric Pugh (Jira)

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

Tim Allison edited comment on TIKA-2925 at 11/27/19 2:10 PM:
-------------------------------------------------------------

[~tilman], thank you for raising these items for discussion.

1. com.pff:java-libpst -- I didn't upgrade that because of this: https://issues.apache.org/jira/browse/TIKA-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16324009#comment-16324009

cc [~lfcnassif]

2. metadata-extractor -- I didn't upgrade that because of the change in namespace, and I was worried that'd break code for people using our xmp module.  I asked privately if we could get anyone at Adobe to release their xmp module without the internal namespace.  I haven't heard anything back.  If anyone knows anyone at Adobe who would be willing to do this, please, please do ask.  

I was wondering if we could shade+relocate that library in the near term to get rid of the {{internal.}} namespace. Thoughts?

3. edu.ucar:grib -- I didn't upgrade that because the jump in major version # frightened me.  I _think_ I tried to upgrade it earlier, and I would have had do redo a bunch of our code...this could be a faulty memory.

So, my preference would be to put off 1) until libpst is fixed, 2) until we have success with shade+relocating or another solution and 3) until someone who knows that library can upgrade our code.

What do you and fellow devs think?


was (Author: [hidden email]):
[~tilman], thank you for raising these items for discussion.

1. com.pff:java-libpst -- I didn't upgrade that because of this: https://issues.apache.org/jira/browse/TIKA-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16324009#comment-16324009

2. metadata-extractor -- I didn't upgrade that because of the change in namespace, and I was worried that'd break code for people using our xmp module.  I asked privately if we could get anyone at Adobe to release their xmp module without the internal namespace.  I haven't heard anything back.  If anyone knows anyone at Adobe who would be willing to do this, please, please do ask.  

I was wondering if we could shade+relocate that library in the near term to get rid of the {{internal.}} namespace. Thoughts?

3. edu.ucar:grib -- I didn't upgrade that because the jump in major version # frightened me.  I _think_ I tried to upgrade it earlier, and I would have had do redo a bunch of our code...this could be a faulty memory.

So, my preference would be to put off 1) until libpst is fixed, 2) until we have success with shade+relocating or another solution and 3) until someone who knows that library can upgrade our code.

What do you and fellow devs think?

> General dependency/plugin upgrades for 1.23
> -------------------------------------------
>
>                 Key: TIKA-2925
>                 URL: https://issues.apache.org/jira/browse/TIKA-2925
>             Project: Tika
>          Issue Type: Bug
>            Reporter: Tim Allison
>            Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)