[jira] [Updated] (NUTCH-2979) Upgrade Commons Text to 1.10.0
[ https://issues.apache.org/jira/browse/NUTCH-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Nagel updated NUTCH-2979: --- Labels: help-wanted (was: ) > Upgrade Commons Text to 1.10.0 > -- > > Key: NUTCH-2979 > URL: https://issues.apache.org/jira/browse/NUTCH-2979 > Project: Nutch > Issue Type: Bug > Components: build >Affects Versions: 1.19 >Reporter: Sebastian Nagel >Priority: Major > Labels: help-wanted > Fix For: 1.20 > > > In order to address > [CVE-2022-42889|https://nvd.nist.gov/vuln/detail/CVE-2022-42889] we should > upgrade to commons-text 1.10.0: > - Nutch core depends on 1.4 which is not affected by the CVE > - the plugins lib-htmlunit and any23 depend on a vulnerable commons-text > version (1.5 - 1.9) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NUTCH-2979) Upgrade Commons Text to 1.10.0
Sebastian Nagel created NUTCH-2979: -- Summary: Upgrade Commons Text to 1.10.0 Key: NUTCH-2979 URL: https://issues.apache.org/jira/browse/NUTCH-2979 Project: Nutch Issue Type: Bug Components: build Affects Versions: 1.19 Reporter: Sebastian Nagel Fix For: 1.20 In order to address [CVE-2022-42889|https://nvd.nist.gov/vuln/detail/CVE-2022-42889] we should upgrade to commons-text 1.10.0: - Nutch core depends on 1.4 which is not affected by the CVE - the plugins lib-htmlunit and any23 depend on a vulnerable commons-text version (1.5 - 1.9) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NUTCH-2978) Move to slf4j2 and remove log4j1 and reload4j
[
https://issues.apache.org/jira/browse/NUTCH-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651243#comment-17651243
]
Markus Jelsma edited comment on NUTCH-2978 at 12/22/22 11:33 AM:
-
Ah nope, this is not it. Parse-tika throws lots of errors and stack traces,
although it does work. We now get:
{color:#00}java.util.ServiceConfigurationError:
org.apache.logging.log4j.spi.Provider:
org.apache.logging.log4j.core.impl.Log4jProvider not a subtype
{color}
{color:#00}There are no multiple versions of the same logging JARs anywhere
on the classpath.{color}
was (Author: markus17):
Ah nope, this is not it. Parse-tika throws lots of errors and stack traces,
although it does work. We now get:
{color:#00}java.util.ServiceConfigurationError:
org.apache.logging.log4j.spi.Provider:
org.apache.logging.log4j.core.impl.Log4jProvider not a subtype{color}
> Move to slf4j2 and remove log4j1 and reload4j
> -
>
> Key: NUTCH-2978
> URL: https://issues.apache.org/jira/browse/NUTCH-2978
> Project: Nutch
> Issue Type: Task
>Reporter: Markus Jelsma
>Priority: Major
> Attachments: NUTCH-2978-1.patch, NUTCH-2978-2.patch,
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, NUTCH-2978.patch
>
>
> I got in trouble upgrading some dependencies and got a lot of LinkageErrors
> today, or with a Tika upgrade, disappearing logs. This patch fixes that by
> moving to slf4j2, using the corrent log4j2-slfj4-impl2 and getting rid of old
> log4j -> reload4j.
>
> This patch fixes it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NUTCH-2978) Move to slf4j2 and remove log4j1 and reload4j
[
https://issues.apache.org/jira/browse/NUTCH-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651243#comment-17651243
]
Markus Jelsma commented on NUTCH-2978:
--
Ah nope, this is not it. Parse-tika throws lots of errors and stack traces,
although it does work. We now get:
{color:#00}java.util.ServiceConfigurationError:
org.apache.logging.log4j.spi.Provider:
org.apache.logging.log4j.core.impl.Log4jProvider not a subtype{color}
> Move to slf4j2 and remove log4j1 and reload4j
> -
>
> Key: NUTCH-2978
> URL: https://issues.apache.org/jira/browse/NUTCH-2978
> Project: Nutch
> Issue Type: Task
>Reporter: Markus Jelsma
>Priority: Major
> Attachments: NUTCH-2978-1.patch, NUTCH-2978-2.patch,
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, NUTCH-2978.patch
>
>
> I got in trouble upgrading some dependencies and got a lot of LinkageErrors
> today, or with a Tika upgrade, disappearing logs. This patch fixes that by
> moving to slf4j2, using the corrent log4j2-slfj4-impl2 and getting rid of old
> log4j -> reload4j.
>
> This patch fixes it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
