You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/12/20 18:25:00 UTC

[jira] [Commented] (JENA-2227) Logging artifacts cleanup

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

ASF subversion and git services commented on JENA-2227:
-------------------------------------------------------

Commit 70d6faa828aa79eb9665490c37b7fc8d12e20b2b in jena's branch refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=70d6faa ]

Merge pull request #1139 from afs/logging

JENA-2227: Logging artifacts cleanup

> Logging artifacts cleanup
> -------------------------
>
>                 Key: JENA-2227
>                 URL: https://issues.apache.org/jira/browse/JENA-2227
>             Project: Apache Jena
>          Issue Type: Task
>    Affects Versions: Jena 4.3.2
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>             Fix For: Jena 4.4.0
>
>
> Following on from JENA-2215 and log4j2 updates, this ticket is for some maintenance of log4j artifact inclusion to only depend on the minimum necessary
> None of these changes are security related.
> Some seem to be possible because log4j2 has refined its scoping and dependency handling since Jena usage was setup (several log4j2 versions ago - well before the recent security fixes.)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)