You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2018/08/31 13:23:00 UTC

[jira] [Resolved] (JENA-1595) Move log4j into scope test in the parent POM

     [ https://issues.apache.org/jira/browse/JENA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne resolved JENA-1595.
---------------------------------
    Resolution: Fixed

Done with

https://github.com/apache/jena/commit/a17c6dd732ca32ef4122dc089c8717fccc5b75b1

> Move log4j into scope test in the parent POM
> --------------------------------------------
>
>                 Key: JENA-1595
>                 URL: https://issues.apache.org/jira/browse/JENA-1595
>             Project: Apache Jena
>          Issue Type: Task
>          Components: Build
>    Affects Versions: Jena 3.8.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>             Fix For: Jena 3.9.0
>
>
> Having dependencies in the parent POM restricts the ability to exclude them.
> Many of the modules rely on log4j for testing.
> Changing the parent dependency to scope-test provides a way to catch all uses in testing.
> This is a step towards refactoring logging.
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)