[jira] [Commented] (JENA-1005) Move off Log4j v1.

2015-11-08 Thread Andy Seaborne (JIRA)

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

Andy Seaborne commented on JENA-1005:
-

Log4j2, as of version 2.4, supports a java properties syntax.  It is not the 
same as Log4j 1, but for the use made by Jena it is quite close and seems to 
have the right features.

http://logging.apache.org/log4j/2.x/manual/configuration.html#Properties


> Move off Log4j v1.
> --
>
> Key: JENA-1005
> URL: https://issues.apache.org/jira/browse/JENA-1005
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Minor
>
> Log4J v1 is approaching end-of-life.  Jena uses slf4j for logging from code.
> Jena depends on log4j for controlling output in tests and for the output in 
> commands. This is in the log4j explicit control utilities.
> Choices include:
> * Log4jv2 log4j v2 does not support log4j.properties.
> * Use java.util.logging (JUL) in some or all of those places.
> Others?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (JENA-1005) Move off Log4j v1.

2016-09-03 Thread Andy Seaborne (JIRA)

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

Andy Seaborne commented on JENA-1005:
-

Jena uses slf4j exclusively for logging output and a provider of  log4j v1 as 
an {{}} dependency.

The uses are:

* Module jena-cmds
* Module jena-base has logging setup code
* Fuseki has logging setup code with internal defaults
* Testing - Jena needs some logging provider to run during tests.

As of Sept 2016:

|| POM File || Notes ||
| jena-parent/pom.xml   | Dependency, version and 
{{}}
| jena-fuseki1/pom.xml  | Fuseki1 logging
| jena-core/pom.xml | Surefire configuration
| jena-spatial/pom.xml  | Surefire configuration
| jena-fuseki2/jena-fuseki-war/pom.xml  | Logging
| jena-fuseki2/jena-fuseki-core/pom.xml |  |
| jena-fuseki2/jena-fuseki-embedded/pom.xml | Excludes all log4j
| jena-csv/pom.xml  | Surefire configuration
| jena-jdbc/jena-jdbc-core/pom.xml  | Jena Driver configures Log4j 
directly
| jena-cmds/pom.xml | Cmd output via fixed string
|| Assembly files || ||
| apache-jena/assembly-jena-zip.xml | Legacy for rdfcat?
| jena-fuseki1/assembly-dist.xml | |
| jena-fuseki2/apache-jena-fuseki/assembly-dist.xml | |
|| Other || ||
| apache-jena/jena-log4j.properties | Legacy for rdfcat?
| jena-arq/log4j.properties| Stray?
| jena-sdb/log4j.properties| SDB commands?
| jena-tdb/log4j.properties| Stray?

\\

|| Configuration Files - src/main ||
| jena-core/src/main/resources/jena-log4j.properties |
| 
jena-fuseki2/jena-fuseki-core/src/main/resources/org/apache/jena/fuseki/log4j.properties
 |
| jena-jdbc/jena-jdbc-core/src/main/resources/jena-jdbc-log4j.properties |
|| Configuration Files - src/test ||
| jena-core/src/test/resources/jena-test-log4j.properties |
| jena-arq/src/test/resources/log4j.properties |
| jena-arq/src/test/resources/log4j-testing.properties |
| jena-text/src/test/resources/log4j.properties |
| jena-maven-tools/src/test/resources/log4j.properties |
| jena-fuseki1/src/test/resources/log4j.properties |
| jena-permissions/src/test/resources/log4j.properties |
| jena-spatial/src/test/resources/log4j.properties |
| jena-csv/src/test/resources/log4j.properties |
| jena-jdbc/jena-jdbc-driver-remote/src/test/resources/log4j.properties |
| jena-jdbc/jena-jdbc-driver-tdb/src/test/resources/log4j.properties |
| jena-jdbc/jena-jdbc-driver-mem/src/test/resources/log4j.properties |
| jena-jdbc/jena-jdbc-driver-bundle/src/test/resources/log4j.properties |
| jena-jdbc/jena-jdbc-core/src/test/resources/log4j.properties |
| jena-elephas/jena-elephas-common/src/test/resources/log4j.properties |
| jena-elephas/jena-elephas-io/src/test/resources/log4j.properties |
| jena-elephas/jena-elephas-mapreduce/src/test/resources/log4j.properties |


> Move off Log4j v1.
> --
>
> Key: JENA-1005
> URL: https://issues.apache.org/jira/browse/JENA-1005
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Minor
>
> Log4J v1 is approaching end-of-life.  Jena uses slf4j for logging from code.
> Jena depends on log4j for controlling output in tests and for the output in 
> commands. This is in the log4j explicit control utilities.
> Choices include:
> * Log4jv2 log4j v2 does not support log4j.properties.
> * Use java.util.logging (JUL) in some or all of those places.
> Others?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (JENA-1005) Move off Log4j v1.

2020-02-19 Thread ASF subversion and git services (Jira)


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

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

Commit 9cc1b65d7a765004f13bd18f413b58e3387afd78 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=9cc1b65 ]

Merge pull request #690 from afs/test-logging

JENA-1005: Isolate log4j1 usage in tests.

> Move off Log4j v1.
> --
>
> Key: JENA-1005
> URL: https://issues.apache.org/jira/browse/JENA-1005
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Log4J v1 is approaching end-of-life.  Jena uses slf4j for logging from code.
> Jena depends on log4j for controlling output in tests and for the output in 
> commands. This is in the log4j explicit control utilities.
> Choices include:
> * Log4jv2 log4j v2 does not support log4j.properties.
> * Use java.util.logging (JUL) in some or all of those places.
> Others?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1005) Move off Log4j v1.

2020-02-19 Thread ASF subversion and git services (Jira)


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

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

Commit 2e136071fc278debd461888bbeaf716f0b0bda18 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=2e13607 ]

JENA-1005: Isolate log4j1 usage in tests.

Put in log4j2 dependency settings
Update slj4j to 1.7.30
Put log4j2 operations into LogCtl


> Move off Log4j v1.
> --
>
> Key: JENA-1005
> URL: https://issues.apache.org/jira/browse/JENA-1005
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Log4J v1 is approaching end-of-life.  Jena uses slf4j for logging from code.
> Jena depends on log4j for controlling output in tests and for the output in 
> commands. This is in the log4j explicit control utilities.
> Choices include:
> * Log4jv2 log4j v2 does not support log4j.properties.
> * Use java.util.logging (JUL) in some or all of those places.
> Others?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1005) Move off Log4j v1.

2020-03-20 Thread ASF subversion and git services (Jira)


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

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

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

JENA-1005: Switch from log4j1 to log4j2


> Move off Log4j v1.
> --
>
> Key: JENA-1005
> URL: https://issues.apache.org/jira/browse/JENA-1005
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Minor
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Log4J v1 is approaching end-of-life.  Jena uses slf4j for logging from code.
> Jena depends on log4j for controlling output in tests and for the output in 
> commands. This is in the log4j explicit control utilities.
> Choices include:
> * Log4jv2 log4j v2 does not support log4j.properties.
> * Use java.util.logging (JUL) in some or all of those places.
> Others?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (JENA-1005) Move off Log4j v1.

2020-03-20 Thread ASF subversion and git services (Jira)


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

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

Commit 9b7c17bcd55c56118dfcbe5287cf36a92cc11e7e in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=9b7c17b ]

Merge pull request #710 from afs/logging

JENA-1005: Switch from log4j1 to log4j2

> Move off Log4j v1.
> --
>
> Key: JENA-1005
> URL: https://issues.apache.org/jira/browse/JENA-1005
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Minor
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Log4J v1 is approaching end-of-life.  Jena uses slf4j for logging from code.
> Jena depends on log4j for controlling output in tests and for the output in 
> commands. This is in the log4j explicit control utilities.
> Choices include:
> * Log4jv2 log4j v2 does not support log4j.properties.
> * Use java.util.logging (JUL) in some or all of those places.
> Others?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)