[
https://issues.apache.org/jira/browse/TIKA-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698313#comment-14698313
]
Uwe Schindler edited comment on TIKA-1706 at 8/15/15 3:19 PM:
--------------------------------------------------------------
Yes, you can add the maven property
{{<failOnUnresolvableSignatures>false</failOnUnresolvableSignatures>}} to the
plugin configuration:
[http://jenkins.thetaphi.de/job/Forbidden-APIs/javadoc/check-mojo.html#failOnUnresolvableSignatures]
An alternative is to only enable commons-io-unsafe-2.4 only for those modules
where its used, unfortunately this is not so easy, because you cannot "inherit"
only some array values to submodules, you miust reconfigure all
bundledsignatures in submodules.
was (Author: thetaphi):
Yes, you can add the maven property
{{<failOnUnresolvableSignatures>false</failOnUnresolvableSignatures>" to the
plugin configuration}}:
[http://jenkins.thetaphi.de/job/Forbidden-APIs/javadoc/check-mojo.html#failOnUnresolvableSignatures]
An alternative is to only enable commons-io-unsafe-2.4 only for those modules
where its used, unfortunately this is not so easy, because you cannot "inherit"
only some array values to submodules, you miust reconfigure all
bundledsignatures in submodules.
> Bring back commons-io to tika-core
> ----------------------------------
>
> Key: TIKA-1706
> URL: https://issues.apache.org/jira/browse/TIKA-1706
> Project: Tika
> Issue Type: Improvement
> Components: core
> Reporter: Yaniv Kunda
> Priority: Minor
> Fix For: 1.11
>
> Attachments: TIKA-1706.patch
>
>
> TIKA-249 inlined select commons-io classes in order to simplify the
> dependency tree and save some space.
> I believe these arguments are weaker nowadays due to the following concerns:
> - Most of the non-core modules already use commons-io, and since tika-core is
> usually not used by itself, commons-io is already included with it
> - Since some modules use both tika-core and commons-io, it's not clear which
> code should be used
> - Having the inlined classes causes more maintenance and/or technology debt
> (which in turn causes more maintenance)
> - Newer commons-io code utilizes newer platform code, e.g. using Charset
> objects instead of encoding names, being able to use StringBuilder instead of
> StringBuffer, and so on.
> I'll be happy to provide a patch to replace usages of the inlined classes
> with commons-io classes if this is accepted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
