[jira] [Commented] (TIKA-2245) Standardise logging

[ https://issues.apache.org/jira/browse/TIKA-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698065#comment-17698065 ] Konstantin Gribov commented on TIKA-2245: - [~lfcnassif], yeah {{commons-logging}} must be excluded

[jira] [Comment Edited] (TIKA-3934) Reogranize POMs parent chain to avoid leaking dependency management downstream

[ https://issues.apache.org/jira/browse/TIKA-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636242#comment-17636242 ] Konstantin Gribov edited comment on TIKA-3934 at 11/19/22 10:31 PM: It

[jira] [Commented] (TIKA-3934) Reogranize POMs parent chain to avoid leaking dependency management downstream

[ https://issues.apache.org/jira/browse/TIKA-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636242#comment-17636242 ] Konstantin Gribov commented on TIKA-3934: - It seems that it doesn't, if I have import for

[jira] [Commented] (TIKA-3934) Reogranize POMs parent chain to avoid leaking dependency management downstream

[ https://issues.apache.org/jira/browse/TIKA-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636239#comment-17636239 ] Konstantin Gribov commented on TIKA-3934: - I need to recheck if Maven inherits parent

[jira] [Commented] (TIKA-3735) Require Java 11 for 2.x at some point

[ https://issues.apache.org/jira/browse/TIKA-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636238#comment-17636238 ] Konstantin Gribov commented on TIKA-3735: - Another thing that comes to mind that we could have

[jira] [Closed] (TIKA-3175) Upgrade version of TPS: commons-io

[ https://issues.apache.org/jira/browse/TIKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-3175. --- > Upgrade version of TPS: commons-io > -- > >

[jira] [Resolved] (TIKA-3175) Upgrade version of TPS: commons-io

[ https://issues.apache.org/jira/browse/TIKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-3175. - Resolution: Duplicate > Upgrade version of TPS: commons-io >

[jira] [Resolved] (TIKA-3387) Unexpected RuntimeException from org.apache.tika.parser.microsoft.ooxml.OOXMLParser

[ https://issues.apache.org/jira/browse/TIKA-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-3387. - Resolution: Incomplete Please feel free to reopen the issue if it can be reproduced with

[jira] [Resolved] (TIKA-3712) update jackson-databind to 2.13.2.1 or greater in tika jars

[ https://issues.apache.org/jira/browse/TIKA-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-3712. - Resolution: Fixed > update jackson-databind to 2.13.2.1 or greater in tika jars >

[jira] [Updated] (TIKA-3712) update jackson-databind to 2.13.2.1 or greater in tika jars

[ https://issues.apache.org/jira/browse/TIKA-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3712: Fix Version/s: 2.4.1 > update jackson-databind to 2.13.2.1 or greater in tika jars >

[jira] [Created] (TIKA-3935) Remove log4j 1.2.x from dependencies

Konstantin Gribov created TIKA-3935: --- Summary: Remove log4j 1.2.x from dependencies Key: TIKA-3935 URL: https://issues.apache.org/jira/browse/TIKA-3935 Project: Tika Issue Type: Task

[jira] [Commented] (TIKA-3324) Add checkstyle checker

[ https://issues.apache.org/jira/browse/TIKA-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636228#comment-17636228 ] Konstantin Gribov commented on TIKA-3324: - I certainly lost against checkstyle plugin. When I just

[jira] [Updated] (TIKA-3934) Reogranize POMs parent chain to avoid leaking dependency management downstream

[ https://issues.apache.org/jira/browse/TIKA-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3934: Fix Version/s: 2.6.1 > Reogranize POMs parent chain to avoid leaking dependency management

[jira] [Updated] (TIKA-3934) Reogranize POMs parent chain to avoid leaking dependency management downstream

[ https://issues.apache.org/jira/browse/TIKA-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3934: Description: Tika's BOM (Bill of Materials) artifact has {{tika-parent}} as a parent POM

[jira] [Created] (TIKA-3934) Reogranize POMs parent chain to avoid leaking dependency management downstream

Konstantin Gribov created TIKA-3934: --- Summary: Reogranize POMs parent chain to avoid leaking dependency management downstream Key: TIKA-3934 URL: https://issues.apache.org/jira/browse/TIKA-3934

[jira] [Closed] (TIKA-3368) Add Bill of Materials (BOM) artifact (Tika 1.x)

[ https://issues.apache.org/jira/browse/TIKA-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-3368. --- > Add Bill of Materials (BOM) artifact (Tika 1.x) >

[jira] [Resolved] (TIKA-3368) Add Bill of Materials (BOM) artifact (Tika 1.x)

[ https://issues.apache.org/jira/browse/TIKA-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-3368. - Resolution: Invalid Tika 1.x reached EOL and PR was closed some time ago, just a JIRA

[jira] [Updated] (TIKA-3368) Add Bill of Materials (BOM) artifact (Tika 1.x)

[ https://issues.apache.org/jira/browse/TIKA-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3368: Fix Version/s: 1.27 (was: 2.0.0-BETA) > Add Bill of Materials (BOM)

[jira] [Updated] (TIKA-3367) Add Bill of Materials (BOM) artifact

[ https://issues.apache.org/jira/browse/TIKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3367: Fix Version/s: 2.3.0 (was: 2.1.0) > Add Bill of Materials (BOM)

[jira] [Resolved] (TIKA-3367) Add Bill of Materials (BOM) artifact

[ https://issues.apache.org/jira/browse/TIKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-3367. - Resolution: Fixed > Add Bill of Materials (BOM) artifact >

[jira] [Closed] (TIKA-3367) Add Bill of Materials (BOM) artifact

[ https://issues.apache.org/jira/browse/TIKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-3367. --- > Add Bill of Materials (BOM) artifact > > >

[jira] [Commented] (TIKA-3493) dcterms:created date depends on the current TimeZone in RTF documents

[ https://issues.apache.org/jira/browse/TIKA-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635951#comment-17635951 ] Konstantin Gribov commented on TIKA-3493: - Just hit the same with one of the tests failing. I

[jira] [Commented] (TIKA-3906) Build a new version of the Tika docker image to fix CVEs

[ https://issues.apache.org/jira/browse/TIKA-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625204#comment-17625204 ] Konstantin Gribov commented on TIKA-3906: - +1 on such versioning scheme, it should be transparent

[jira] [Commented] (TIKA-3666) Detect and indicate file encrypted with Rights Management Service RMS/IRM

[ https://issues.apache.org/jira/browse/TIKA-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484950#comment-17484950 ] Konstantin Gribov commented on TIKA-3666: - When I looked into MS AD RMS some time ago it wasn't

[jira] [Resolved] (TIKA-3631) Upgrade log4j 2 to version 2.17.0 in tika

[ https://issues.apache.org/jira/browse/TIKA-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-3631. - Resolution: Fixed > Upgrade log4j 2 to version 2.17.0 in tika >

[jira] [Commented] (TIKA-3632) Log4j appears to be running in a Servlet environment, but there's no log4j-web module available

[ https://issues.apache.org/jira/browse/TIKA-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463513#comment-17463513 ] Konstantin Gribov commented on TIKA-3632: - I'll look into it. Seems it should be added from first

[jira] [Assigned] (TIKA-3632) Log4j appears to be running in a Servlet environment, but there's no log4j-web module available

[ https://issues.apache.org/jira/browse/TIKA-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov reassigned TIKA-3632: --- Assignee: Konstantin Gribov > Log4j appears to be running in a Servlet environment,

[jira] [Commented] (TIKA-3628) Is tika 2.2 available

[ https://issues.apache.org/jira/browse/TIKA-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462557#comment-17462557 ] Konstantin Gribov commented on TIKA-3628: - Great! For gradle-related help beside docs I highly

[jira] [Commented] (TIKA-3628) Is tika 2.2 available

[ https://issues.apache.org/jira/browse/TIKA-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462541#comment-17462541 ] Konstantin Gribov commented on TIKA-3628: - {quote}No cached version of

[jira] [Commented] (TIKA-3628) Is tika 2.2 available

[ https://issues.apache.org/jira/browse/TIKA-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462491#comment-17462491 ] Konstantin Gribov commented on TIKA-3628: - Yeah, I get it that you want to upgrade. 2.2.0 is

[jira] [Commented] (TIKA-3628) Is tika 2.2 available

[ https://issues.apache.org/jira/browse/TIKA-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462482#comment-17462482 ] Konstantin Gribov commented on TIKA-3628: - Maven Central has Tika 2.2.0:

[jira] [Updated] (TIKA-3623) Upgrade log4j to 2.16.0

[ https://issues.apache.org/jira/browse/TIKA-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3623: Priority: Blocker (was: Major) > Upgrade log4j to 2.16.0 > --- > >

[jira] [Updated] (TIKA-3623) Upgrade log4j to 2.16.0

[ https://issues.apache.org/jira/browse/TIKA-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3623: Summary: Upgrade log4j to 2.16.0 (was: Upgrade log4j to 2.0.16) > Upgrade log4j to 2.16.0

[jira] [Updated] (TIKA-3616) Upgrade log4j2 to 2.15.0

[ https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3616: Summary: Upgrade log4j2 to 2.15.0 (was: Upgrade log4j2 to 2.0.15) > Upgrade log4j2 to

[jira] [Commented] (TIKA-3616) Upgrade log4j2

[ https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460168#comment-17460168 ] Konstantin Gribov commented on TIKA-3616: - I looked a bit how Tika and it's upstream dependencies

[jira] [Updated] (TIKA-3367) Add Bill of Materials (BOM) artifact

[ https://issues.apache.org/jira/browse/TIKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3367: Fix Version/s: (was: 2.0.0-BETA) 2.0.1 > Add Bill of Materials (BOM)

[jira] [Updated] (TIKA-3164) Upgrade to POI 5.0.0 when available

[ https://issues.apache.org/jira/browse/TIKA-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3164: Issue Type: Task (was: Bug) > Upgrade to POI 5.0.0 when available >

[jira] [Commented] (TIKA-3312) Support Log4j2 jar in Tika-app.jar

[ https://issues.apache.org/jira/browse/TIKA-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17331234#comment-17331234 ] Konstantin Gribov commented on TIKA-3312: - [~tallison], will do. I took a peek into it right now

[jira] [Closed] (TIKA-3149) Tikka 1.18 not working with tess4j 3.4.8 on linux

[ https://issues.apache.org/jira/browse/TIKA-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-3149. --- > Tikka 1.18 not working with tess4j 3.4.8 on linux >

[jira] [Updated] (TIKA-3149) Tikka 1.18 not working with tess4j 3.4.8 on linux

[ https://issues.apache.org/jira/browse/TIKA-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3149: Description: I am using tikka 1.18 version to parse the docuemtn content. It is working

[jira] [Resolved] (TIKA-3149) Tikka 1.18 not working with tess4j 3.4.8 on linux

[ https://issues.apache.org/jira/browse/TIKA-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-3149. - Assignee: Konstantin Gribov Resolution: Not A Bug > Tikka 1.18 not working with

[jira] [Commented] (TIKA-3149) Tikka 1.18 not working with tess4j 3.4.8 on linux

[ https://issues.apache.org/jira/browse/TIKA-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17331122#comment-17331122 ] Konstantin Gribov commented on TIKA-3149: - You have both slf4j-jdk14 (logger implementation using

[jira] [Updated] (TIKA-3369) Flaky Tesseract OCR confirmMultiPageTiffHandling test

[ https://issues.apache.org/jira/browse/TIKA-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3369: Description: Current main@08793d360a838db04a3d23b902c34d9e6e7362e4 fails with {noformat}

[jira] [Created] (TIKA-3369) Flaky Tesseract OCR confirmMultiPageTiffHandling test

Konstantin Gribov created TIKA-3369: --- Summary: Flaky Tesseract OCR confirmMultiPageTiffHandling test Key: TIKA-3369 URL: https://issues.apache.org/jira/browse/TIKA-3369 Project: Tika Issue

[jira] [Created] (TIKA-3368) Add Bill of Materials (BOM) artifact (Tika 1.x)

Konstantin Gribov created TIKA-3368: --- Summary: Add Bill of Materials (BOM) artifact (Tika 1.x) Key: TIKA-3368 URL: https://issues.apache.org/jira/browse/TIKA-3368 Project: Tika Issue Type:

[jira] [Updated] (TIKA-3367) Add Bill of Materials (BOM) artifact

[ https://issues.apache.org/jira/browse/TIKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-3367: Fix Version/s: (was: 1.27) > Add Bill of Materials (BOM) artifact >

[jira] [Created] (TIKA-3367) Add Bill of Materials (BOM) artifact

Konstantin Gribov created TIKA-3367: --- Summary: Add Bill of Materials (BOM) artifact Key: TIKA-3367 URL: https://issues.apache.org/jira/browse/TIKA-3367 Project: Tika Issue Type:

[jira] [Commented] (TIKA-3312) Support Log4j2 jar in Tika-app.jar

[ https://issues.apache.org/jira/browse/TIKA-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298345#comment-17298345 ] Konstantin Gribov commented on TIKA-3312: - [~tallison], in that case I think it could safely go

[jira] [Commented] (TIKA-3312) Support Log4j2 jar in Tika-app.jar

[ https://issues.apache.org/jira/browse/TIKA-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298099#comment-17298099 ] Konstantin Gribov commented on TIKA-3312: - I agree that we should upgrade to log4j2 or

[jira] [Commented] (TIKA-3120) Remove whitelist/blacklist terminology

[ https://issues.apache.org/jira/browse/TIKA-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146315#comment-17146315 ] Konstantin Gribov commented on TIKA-3120: - [~tallison], I noticed messages from commits@tika.a.o

[jira] [Commented] (TIKA-3121) Rename master branch

[ https://issues.apache.org/jira/browse/TIKA-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146290#comment-17146290 ] Konstantin Gribov commented on TIKA-3121: - Alternative is to use just branches like main,

[jira] [Commented] (TIKA-3121) Rename master branch

[ https://issues.apache.org/jira/browse/TIKA-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146288#comment-17146288 ] Konstantin Gribov commented on TIKA-3121: - I didn't vote before and a bit ambivalent about change.

[jira] [Commented] (TIKA-3082) Consider adding an OpenAPI for tika-server

[ https://issues.apache.org/jira/browse/TIKA-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073020#comment-17073020 ] Konstantin Gribov commented on TIKA-3082: - Also we could later add client modules for couple of

[jira] [Commented] (TIKA-3082) Consider adding an OpenAPI for tika-server

[ https://issues.apache.org/jira/browse/TIKA-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073017#comment-17073017 ] Konstantin Gribov commented on TIKA-3082: - [~lewismc], my gratitude and big +1 than) In my

[jira] [Commented] (TIKA-3082) Consider adding an OpenAPI for tika-server

[ https://issues.apache.org/jira/browse/TIKA-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072957#comment-17072957 ] Konstantin Gribov commented on TIKA-3082: - [~lewismc], could you please clarify how do you wish to

[jira] [Commented] (TIKA-3073) Add gzip in- and out- interceptors to tika-server

[ https://issues.apache.org/jira/browse/TIKA-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062662#comment-17062662 ] Konstantin Gribov commented on TIKA-3073: - [~tallison], glad to help. I'm unfamiliar with CXF so

[jira] [Comment Edited] (TIKA-3073) Add compression option to /rmeta output

[ https://issues.apache.org/jira/browse/TIKA-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061672#comment-17061672 ] Konstantin Gribov edited comment on TIKA-3073 at 3/18/20, 12:32 PM:

[jira] [Comment Edited] (TIKA-3073) Add compression option to /rmeta output

[ https://issues.apache.org/jira/browse/TIKA-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061672#comment-17061672 ] Konstantin Gribov edited comment on TIKA-3073 at 3/18/20, 12:31 PM:

[jira] [Commented] (TIKA-3073) Add compression option to /rmeta output

[ https://issues.apache.org/jira/browse/TIKA-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061672#comment-17061672 ] Konstantin Gribov commented on TIKA-3073: - [~tallison], usually webserver should accept HTTP

[jira] [Commented] (TIKA-3019) [9.8] [CVE-2019-17571] [tika-app] [1.23]

[ https://issues.apache.org/jira/browse/TIKA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016096#comment-17016096 ] Konstantin Gribov commented on TIKA-3019: - [~rgoers], yes, I mentioned {{log4j1.compatibility}}

[jira] [Closed] (TIKA-3018) log4j 1.2 version used by Apache Tika 1.23 is vulnerable to CVE-2019-17571

[ https://issues.apache.org/jira/browse/TIKA-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-3018. --- > log4j 1.2 version used by Apache Tika 1.23 is vulnerable to CVE-2019-17571 >

[jira] [Resolved] (TIKA-3018) log4j 1.2 version used by Apache Tika 1.23 is vulnerable to CVE-2019-17571

[ https://issues.apache.org/jira/browse/TIKA-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-3018. - Resolution: Duplicate > log4j 1.2 version used by Apache Tika 1.23 is vulnerable to

[jira] [Commented] (TIKA-3019) [9.8] [CVE-2019-17571] [tika-app] [1.23]

[ https://issues.apache.org/jira/browse/TIKA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17013000#comment-17013000 ] Konstantin Gribov commented on TIKA-3019: - [~tallison], there seems to be actually twofold issue

[jira] [Closed] (TIKA-2601) Invalid XHTML output (overlapping a and formatting tags) for some WORD documents

[ https://issues.apache.org/jira/browse/TIKA-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-2601. --- > Invalid XHTML output (overlapping a and formatting tags) for some WORD > documents >

[jira] [Closed] (TIKA-879) Detection problem: message/rfc822 file is detected as text/plain.

[ https://issues.apache.org/jira/browse/TIKA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-879. -- > Detection problem: message/rfc822 file is detected as text/plain. >

[jira] [Closed] (TIKA-2209) Update PDFBox to 2.0.4

[ https://issues.apache.org/jira/browse/TIKA-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-2209. --- > Update PDFBox to 2.0.4 > -- > > Key: TIKA-2209 >

[jira] [Closed] (TIKA-2681) Upgrade to PDFBox 2.0.11

[ https://issues.apache.org/jira/browse/TIKA-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-2681. --- > Upgrade to PDFBox 2.0.11 > > > Key: TIKA-2681 >

[jira] [Closed] (TIKA-2622) Upgrade to PDFBox 2.0.10 when available

[ https://issues.apache.org/jira/browse/TIKA-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-2622. --- > Upgrade to PDFBox 2.0.10 when available > --- > >

[jira] [Resolved] (TIKA-2566) Move logging in tika-core to slf4j-api (with log4j in test scope) as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-2566. - Resolution: Fixed > Move logging in tika-core to slf4j-api (with log4j in test scope) as

[jira] [Updated] (TIKA-2566) Move logging in tika-core to slf4j-api (with log4j in test scope) as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-2566: Summary: Move logging in tika-core to slf4j-api (with log4j in test scope) as we do in the

[jira] [Resolved] (TIKA-2314) Migrate logging to slf4j in master (2.x) branch

[ https://issues.apache.org/jira/browse/TIKA-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-2314. - Resolution: Resolved > Migrate logging to slf4j in master (2.x) branch >

[jira] [Closed] (TIKA-2315) Update logging page at wiki with actual info

[ https://issues.apache.org/jira/browse/TIKA-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-2315. --- > Update logging page at wiki with actual info > > >

[jira] [Resolved] (TIKA-2315) Update logging page at wiki with actual info

[ https://issues.apache.org/jira/browse/TIKA-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-2315. - Resolution: Fixed > Update logging page at wiki with actual info >

[jira] [Updated] (TIKA-2314) Migrate logging to slf4j in master (2.x) branch

[ https://issues.apache.org/jira/browse/TIKA-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-2314: Summary: Migrate logging to slf4j in master (2.x) branch (was: Migrate logging to slf4j in

[jira] [Updated] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-2566: Fix Version/s: (was: 1.20) > Move logging in tika-core to log4j via slf4j as we do in

[jira] [Resolved] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-2566. - Resolution: Fixed Fix Version/s: 1.20 > Move logging in tika-core to log4j via

[jira] [Reopened] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov reopened TIKA-2566: - > Move logging in tika-core to log4j via slf4j as we do in the rest of Tika >

[jira] [Resolved] (TIKA-2555) Text with [underline] + [another format] in word document generates overlapping html tags.

[ https://issues.apache.org/jira/browse/TIKA-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-2555. - Resolution: Fixed Fix Version/s: 1.21 2.0 > Text with

[jira] [Resolved] (TIKA-2601) Invalid XHTML output (overlapping a and formatting tags) for some WORD documents

[ https://issues.apache.org/jira/browse/TIKA-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-2601. - Resolution: Fixed Fix Version/s: 1.21 2.0 > Invalid XHTML

[jira] [Assigned] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov reassigned TIKA-2566: --- Assignee: Konstantin Gribov > Move logging in tika-core to log4j via slf4j as we do

[jira] [Reopened] (TIKA-2601) Invalid XHTML output (overlapping a and formatting tags) for some WORD documents

[ https://issues.apache.org/jira/browse/TIKA-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov reopened TIKA-2601: - Assignee: Konstantin Gribov > Invalid XHTML output (overlapping a and formatting tags)

[jira] [Updated] (TIKA-2601) Invalid XHTML output (overlapping a and formatting tags) for some WORD documents

[ https://issues.apache.org/jira/browse/TIKA-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov updated TIKA-2601: Summary: Invalid XHTML output (overlapping a and formatting tags) for some WORD documents

[jira] [Closed] (TIKA-2347) Underlined text is not decorated as such when extracting from word documents

[ https://issues.apache.org/jira/browse/TIKA-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-2347. --- > Underlined text is not decorated as such when extracting from word documents >

[jira] [Resolved] (TIKA-2601) Invalid XHTML output for some WORD documents

[ https://issues.apache.org/jira/browse/TIKA-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-2601. - Resolution: Duplicate I mark it as duplicate for TIKA-2555 which I'm currently looking

[jira] [Assigned] (TIKA-2555) Text with [underline] + [another format] in word document generates overlapping html tags.

[ https://issues.apache.org/jira/browse/TIKA-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov reassigned TIKA-2555: --- Assignee: Konstantin Gribov > Text with [underline] + [another format] in word

[jira] [Commented] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797354#comment-16797354 ] Konstantin Gribov commented on TIKA-2566: - Just to clarify which option you propose: 1. use

[jira] [Commented] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797288#comment-16797288 ] Konstantin Gribov commented on TIKA-2566: - Since log4j2 has bridge to slf4j-api I'm don't see any

[jira] [Commented] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796251#comment-16796251 ] Konstantin Gribov commented on TIKA-2566: - [~talli...@apache.org], why do you prefer log4j (which

[jira] [Commented] (TIKA-2566) Move logging in tika-core to log4j via slf4j as we do in the rest of Tika

[ https://issues.apache.org/jira/browse/TIKA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796262#comment-16796262 ] Konstantin Gribov commented on TIKA-2566: - JFYI: https://www.slf4j.org/faq.html#changesInVersion18

[jira] [Commented] (TIKA-2245) Standardise logging

[ https://issues.apache.org/jira/browse/TIKA-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796242#comment-16796242 ] Konstantin Gribov commented on TIKA-2245: - [~talli...@apache.org], slf4j-api is quite stable from

[jira] [Comment Edited] (TIKA-2756) Switch to commons-lang 3

[ https://issues.apache.org/jira/browse/TIKA-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693459#comment-16693459 ] Konstantin Gribov edited comment on TIKA-2756 at 11/20/18 4:36 PM: --- FYI,

[jira] [Commented] (TIKA-2756) Switch to commons-lang 3

[ https://issues.apache.org/jira/browse/TIKA-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693459#comment-16693459 ] Konstantin Gribov commented on TIKA-2756: - FYI, issue seems to be present only with old

[jira] [Closed] (TIKA-2721) Exclude Spring (transitive dependency) from tika-parsers

[ https://issues.apache.org/jira/browse/TIKA-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-2721. --- > Exclude Spring (transitive dependency) from tika-parsers >

[jira] [Commented] (TIKA-2552) Upgrade to POI 4.0.0 when available

[ https://issues.apache.org/jira/browse/TIKA-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617718#comment-16617718 ] Konstantin Gribov commented on TIKA-2552: - [~TigerC10], Tim rolled RC1 this weekend, so, hopefully

[jira] [Commented] (TIKA-2716) Sonatype Nexus auditor is reporting that spring framework vesrion used by Tika 1.18 is vulnerable

[ https://issues.apache.org/jira/browse/TIKA-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603335#comment-16603335 ] Konstantin Gribov commented on TIKA-2716: - Won't Fix because {{spring-*}} is excluded from

[jira] [Closed] (TIKA-2716) Sonatype Nexus auditor is reporting that spring framework vesrion used by Tika 1.18 is vulnerable

[ https://issues.apache.org/jira/browse/TIKA-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov closed TIKA-2716. --- Resolution: Won't Fix Assignee: Konstantin Gribov Fix Version/s: 1.19

[jira] [Resolved] (TIKA-2721) Exclude Spring (transitive dependency) from tika-parsers

[ https://issues.apache.org/jira/browse/TIKA-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Gribov resolved TIKA-2721. - Resolution: Fixed > Exclude Spring (transitive dependency) from tika-parsers >

[jira] [Commented] (TIKA-2721) Exclude Spring (transitive dependency) from tika-parsers

[ https://issues.apache.org/jira/browse/TIKA-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603230#comment-16603230 ] Konstantin Gribov commented on TIKA-2721: - All unit & integration tests passed after excluding

[jira] [Created] (TIKA-2721) Exclude Spring (transitive dependency) from tika-parsers

Konstantin Gribov created TIKA-2721: --- Summary: Exclude Spring (transitive dependency) from tika-parsers Key: TIKA-2721 URL: https://issues.apache.org/jira/browse/TIKA-2721 Project: Tika

[jira] [Commented] (TIKA-2680) Email attachments to an email are not extracted

[ https://issues.apache.org/jira/browse/TIKA-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602361#comment-16602361 ] Konstantin Gribov commented on TIKA-2680: - Just my 2c, I've stopped using Tika for RFC822 parsing

  1   2   3   >