date:20211220

This is a vote to release Log4j 2.3.1, a security release for Java 6 users.

Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...

The vote will remain open for as short amount as time as required to vet the
release. All votes are welcome and we encourage everyone to test the release,
but only Logging PMC votes are “officially” counted. As always, at least 3 +1
votes and more positive than negative votes are required.

Changes in this version include:

New features:
* LOG4J2-3198: Pattern layout no longer enables lookups within message text.

Fixed Bugs:
* LOG4J2-3242: Limit JNDI to the java protocol only. JNDI will remain
disabled by default. Rename JNDI enablement property from
'log4j2.enableJndi' to 'log4j2.enableJndiLookup',
'log4j2.enableJndiJms', and 'log4j2.enableJndiContextSelector’.
* LOG4J2-3230: Fix string substitution recursion.

Tag:
a) for a new copy do "git clone https://github.com/apache/logging-log4j2.git";
and then "git checkout tags/log4j-2.3.1-rc1” or just "git clone -b
log4j-2.3.1-rc1 https://github.com/apache/logging-log4j2.git";
b) for an existing working copy to “git pull” and then “git checkout
tags/log4j-2.12.3-rc1”

Web Site: https://logging.staged.apache.org/log4j/log4j-2.3.1/index.html

Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachelogging-1076

Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/

You may download all the Maven artifacts by executing:
wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
https://repository.apache.org/content/repositories/orgapachelogging-1076/org/apache/logging/log4j/.

[VOTE] Release Log4j Kotlin API 1.2.0-rc3

This is a vote to release Log4j Kotlin API version 1.2.0, the next version of 
the Kotlin facade for Log4j2.

Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...

The vote will remain open for 24 hours (or more if required). All votes are 
welcome and we encourage everyone to test the release, but only Logging PMC 
votes are “officially” counted. As always, at least 3 +1 votes and more 
positive than negative votes are required.

Changes in this release include:

* LOG4J2-3218: Update Log4j dependency to 2.17.0.

This is primarily provided to help upgrade transitive dependencies on 
log4j-core which was recently updated to fix CVE-2021-44228, CVE-2021-45046, 
and CVE-2021-45105.

Tag: 
a)  for a new copy do "git clone 
https://github.com/apache/logging-log4j-kotlin.git 
” and then "git checkout 
tags/log4j-api-kotlin-1.2.0-rc3”  or just "git clone -b 
log4j-api-kotlin-1.2.0-rc3 https://github.com/apache/logging-log4j-kotlin.git 
"
b) for an existing working copy to “git pull” and then “git checkout 
tags/log4j-api-kotlin-1.2.0-rc3”

Web Site: https://logging.staged.apache.org/log4j/kotlin/index.html 


Maven Artifacts: 
https://repository.apache.org/content/repositories/orgapachelogging-1075/

Distribution archives: 
https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/ 


You may download all the Maven artifacts by executing:
wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate 
https://repository.apache.org/content/repositories/orgapachelogging-1075/org/apache/logging/log4j/
 


 --
Matt Sicker

Re: [VOTE] Release Apache Log4j 2.12.3-rc1

2021-12-20 Thread Carter Kozak

+1

-ck

> On Dec 20, 2021, at 22:46, Matt Sicker  wrote:
> 
> +1
> 
> Notes on the release:
> * Sigs and checksums good
> * Builds and tests fine
> * Outdated copyright year in NOTICE.txt
> 
> --
> Matt Sicker
> 
>> On Dec 20, 2021, at 18:52, Ralph Goers  wrote:
>> 
>> This is a vote to release Log4j 2.12.3, a security release for Java 7 users.
>> 
>> Please download, test, and cast your votes on the log4j developers list.
>> [] +1, release the artifacts
>> [] -1, don't release because...
>> 
>> The vote will remain open for as short amount as time as required to vet the 
>> release. All votes are welcome and we encourage everyone to test the 
>> release, but only Logging PMC votes are “officially” counted. As always, at 
>> least 3 +1 votes and more positive than negative votes are required.
>> 
>> Changes in this version include:
>> 
>> Fixed Bugs
>> 
>>• LOG4J2-3230: Fix string substitution recursion.
>>• LOG4J2-3242: Limit JNDI to the java protocol only. JNDI will remain 
>> disabled by default. Rename JNDI enablement property from 
>> 'log4j2.enableJndi' to 'log4j2.enableJndiLookup', 'log4j2.enableJndiJms', 
>> and 'log4j2.enableJndiContextSelector’.
>>   • LOG4J2-2819: Add support for specifying an SSL configuration for 
>> SmtpAppender
>> 
>> Tag: 
>> a)  for a new copy do "git clone 
>> https://github.com/apache/logging-log4j2.git"; and then "git checkout 
>> tags/log4j-2.12.3-rc1”  or just "git clone -b log4j-2.12.3-rc1 
>> https://github.com/apache/logging-log4j2.git";
>> b) for an existing working copy to “git pull” and then “git checkout 
>> tags/log4j-2.12.3-rc1”
>> 
>> Web Site:  https://logging.staged.apache.org/log4j/log4j-2.12.3/index.html
>> 
>> Maven Artifacts: 
>> https://repository.apache.org/content/repositories/orgapachelogging-1074
>> 
>> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/ 
>> 
>> You may download all the Maven artifacts by executing:
>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate 
>> https://repository.apache.org/content/repositories/orgapachelogging-1074/org/apache/logging/log4j/.
>

Re: [VOTE] Release Apache Log4j 2.12.3-rc1

There was a bug in the site build. I checked the fix in to the branch. It 
doesn’t matter for the release.

Ralph

> On Dec 20, 2021, at 6:46 PM, Gary Gregory  wrote:
> 
> Building from the git tag for HEAD detached at log4j-2.12.3-rc1 (2b9359b23)
> 
> - mvn apache-rat:check -DskipTests OK
> - mvn clean install OK except a JVM crash I always get in the
> Cassandra module tests, just like always.
> - mvn site -DskipTests fails with:
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
> project log4j: Error parsing
> '/Users/garydgregory/git/logging-log4j-2.12/src/site/xdoc/manual/appenders.xml':
> line [1713] Error parsing the model: end tag name  must
> match start tag name  from line 1533 (position: TEXT seen
> ...\n\n... @1713:22)  -> [Help 1]
> 
> Is that just me?
> 
> Built with:
> 
> openjdk version "1.8.0_312"
> OpenJDK Runtime Environment (build 1.8.0_312-bre_2021_10_20_23_15-b00)
> OpenJDK 64-Bit Server VM (build 25.312-b00, mixed mode)
> 
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /usr/local/Cellar/maven/3.8.4/libexec
> Java version: 1.8.0_312, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@8/1.8.0+312/libexec/openjdk.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "12.1", arch: "x86_64", family: "mac"
> 
> Darwin *** 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54
> PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64 x86_64
> 
> Gary
> 
> On Mon, Dec 20, 2021 at 7:52 PM Ralph Goers  
> wrote:
>> 
>> This is a vote to release Log4j 2.12.3, a security release for Java 7 users.
>> 
>> Please download, test, and cast your votes on the log4j developers list.
>> [] +1, release the artifacts
>> [] -1, don't release because...
>> 
>> The vote will remain open for as short amount as time as required to vet the 
>> release. All votes are welcome and we encourage everyone to test the 
>> release, but only Logging PMC votes are “officially” counted. As always, at 
>> least 3 +1 votes and more positive than negative votes are required.
>> 
>> Changes in this version include:
>> 
>> Fixed Bugs
>> 
>>• LOG4J2-3230: Fix string substitution recursion.
>>• LOG4J2-3242: Limit JNDI to the java protocol only. JNDI will remain 
>> disabled by default. Rename JNDI enablement property from 
>> 'log4j2.enableJndi' to 'log4j2.enableJndiLookup', 'log4j2.enableJndiJms', 
>> and 'log4j2.enableJndiContextSelector’.
>>• LOG4J2-2819: Add support for specifying an SSL configuration for 
>> SmtpAppender
>> 
>> Tag:
>> a)  for a new copy do "git clone 
>> https://github.com/apache/logging-log4j2.git"; and then "git checkout 
>> tags/log4j-2.12.3-rc1”  or just "git clone -b log4j-2.12.3-rc1 
>> https://github.com/apache/logging-log4j2.git";
>> b) for an existing working copy to “git pull” and then “git checkout 
>> tags/log4j-2.12.3-rc1”
>> 
>> Web Site:  https://logging.staged.apache.org/log4j/log4j-2.12.3/index.html
>> 
>> Maven Artifacts: 
>> https://repository.apache.org/content/repositories/orgapachelogging-1074
>> 
>> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/
>> 
>> You may download all the Maven artifacts by executing:
>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate 
>> https://repository.apache.org/content/repositories/orgapachelogging-1074/org/apache/logging/log4j/.
>

Re: [VOTE] Release Apache Log4j 2.12.3-rc1

+1

Notes on the release:
* Sigs and checksums good
* Builds and tests fine
* Outdated copyright year in NOTICE.txt

--
Matt Sicker

> On Dec 20, 2021, at 18:52, Ralph Goers  wrote:
> 
> This is a vote to release Log4j 2.12.3, a security release for Java 7 users.
> 
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
> 
> The vote will remain open for as short amount as time as required to vet the 
> release. All votes are welcome and we encourage everyone to test the release, 
> but only Logging PMC votes are “officially” counted. As always, at least 3 +1 
> votes and more positive than negative votes are required.
> 
> Changes in this version include:
> 
> Fixed Bugs
> 
>   • LOG4J2-3230: Fix string substitution recursion.
>   • LOG4J2-3242: Limit JNDI to the java protocol only. JNDI will remain 
> disabled by default. Rename JNDI enablement property from 'log4j2.enableJndi' 
> to 'log4j2.enableJndiLookup', 'log4j2.enableJndiJms', and 
> 'log4j2.enableJndiContextSelector’.
>• LOG4J2-2819: Add support for specifying an SSL configuration for 
> SmtpAppender
> 
> Tag: 
> a)  for a new copy do "git clone 
> https://github.com/apache/logging-log4j2.git"; and then "git checkout 
> tags/log4j-2.12.3-rc1”  or just "git clone -b log4j-2.12.3-rc1 
> https://github.com/apache/logging-log4j2.git";
> b) for an existing working copy to “git pull” and then “git checkout 
> tags/log4j-2.12.3-rc1”
> 
> Web Site:  https://logging.staged.apache.org/log4j/log4j-2.12.3/index.html
> 
> Maven Artifacts: 
> https://repository.apache.org/content/repositories/orgapachelogging-1074
> 
> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/ 
> 
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate 
> https://repository.apache.org/content/repositories/orgapachelogging-1074/org/apache/logging/log4j/.

Re: [VOTE] Release Log4j Kotlin API 1.2.0-rc2

I fixed some rat errors, but yeah, looks like I missed that. I’ll cancel this 
and roll a third RC.

—
Matt Sicker

> On Dec 20, 2021, at 20:43, Raman Gupta  wrote:
> 
> As far as I can tell nothing has changed? Did you mean to point to 2.17.0?
> 
>> On Sun, Dec 19, 2021 at 5:52 PM Matt Sicker  wrote:
>> 
>> This is a vote to release Log4j Kotlin API version 1.2.0, the next version
>> of the Kotlin facade for Log4j2.
>> 
>> Please download, test, and cast your votes on the log4j developers list.
>> [] +1, release the artifacts
>> [] -1, don't release because...
>> 
>> The vote will remain open for 72 hours (or more if required). All votes
>> are welcome and we encourage everyone to test the release, but only Logging
>> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
>> positive than negative votes are required.
>> 
>> Changes in this release include:
>> 
>> * LOG4J2-3218: Update Log4j dependency to 2.16.0.
>> 
>> This is primarily provided to help upgrade transitive dependencies on
>> log4j-core which was recently updated to fix CVE-2021-44228 and
>> CVE-2021-45046.
>> 
>> Tag:
>> a)  for a new copy do "git clone
>> https://github.com/apache/logging-log4j-kotlin.git” and then "git
>> checkout tags/log4j-api-kotlin-1.2.0-rc2”  or just "git clone -b
>> log4j-api-kotlin-1.2.0-rc2
>> https://github.com/apache/logging-log4j-kotlin.git";
>> b) for an existing working copy to “git pull” and then “git checkout
>> tags/log4j-api-kotlin-1.2.0-rc2”
>> 
>> Web Site: https://logging.staged.apache.org/log4j/kotlin/index.html
>> 
>> Maven Artifacts:
>> https://repository.apache.org/content/repositories/orgapachelogging-1073/
>> 
>> Distribution archives:
>> https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/
>> 
>> You may download all the Maven artifacts by executing:
>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>> https://repository.apache.org/content/repositories/orgapachelogging-1073/org/apache/logging/log4j/
>> 
>> --
>> Matt Sicker
>> 
>>

Re: [logging-log4j2] 01/01: [DOC] Fix log4j-2.3.x About page incorrect security.html anchor links

I'm not sure this is the right branch, I think log4j-2.3.x is the
right one.

Ralph?

Gary

On Mon, Dec 20, 2021, 21:33  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> rpopma pushed a commit to branch java6
> in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
>
> commit 6e298ba0df07451beced3ed4de2ec71cfdf6b734
> Author: rpopma 
> AuthorDate: Tue Dec 21 11:33:44 2021 +0900
>
> [DOC] Fix log4j-2.3.x About page incorrect security.html anchor links
> ---
>  src/site/xdoc/index.xml | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml
> index b3e8f3f..d289bf7 100644
> --- a/src/site/xdoc/index.xml
> +++ b/src/site/xdoc/index.xml
> @@ -68,7 +68,7 @@
>Upgrade to Log4j 2.3.1 (for Java 6), 2.12.3 (for Java 7), or
> 2.17.0 (for Java 8).
>
>Reference
> -  Please refer to the https://logging.apache.org/log4j/2.x/security.html#CVE-2021-45105";>Security
> page for details and mitigation measures for older versions of
> Log4j.
> +  Please refer to the https://logging.apache.org/log4j/2.x/security.html#CVE-2021-45046";>Security
> page for details and mitigation measures for older versions of
> Log4j.
>
>
>
> @@ -89,7 +89,7 @@
>Upgrade to Log4j 2.3.1 (for Java 6), 2.12.3 (for Java 7), or
> 2.17.0 (for Java 8).
>
>Reference
> -  Please refer to the https://logging.apache.org/log4j/2.x/security.html#CVE-2021-45105";>Security
> page for details and mitigation measures for older versions of
> Log4j.
> +  Please refer to the https://logging.apache.org/log4j/2.x/security.html#CVE-2021-44228";>Security
> page for details and mitigation measures for older versions of
> Log4j.
>
>
>
>

Re: [VOTE] Release Log4j Kotlin API 1.2.0-rc2

2021-12-20 Thread Raman Gupta

As far as I can tell nothing has changed? Did you mean to point to 2.17.0?

On Sun, Dec 19, 2021 at 5:52 PM Matt Sicker  wrote:

> This is a vote to release Log4j Kotlin API version 1.2.0, the next version
> of the Kotlin facade for Log4j2.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
>
> The vote will remain open for 72 hours (or more if required). All votes
> are welcome and we encourage everyone to test the release, but only Logging
> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
> positive than negative votes are required.
>
> Changes in this release include:
>
> * LOG4J2-3218: Update Log4j dependency to 2.16.0.
>
> This is primarily provided to help upgrade transitive dependencies on
> log4j-core which was recently updated to fix CVE-2021-44228 and
> CVE-2021-45046.
>
> Tag:
> a)  for a new copy do "git clone
> https://github.com/apache/logging-log4j-kotlin.git” and then "git
> checkout tags/log4j-api-kotlin-1.2.0-rc2”  or just "git clone -b
> log4j-api-kotlin-1.2.0-rc2
> https://github.com/apache/logging-log4j-kotlin.git";
> b) for an existing working copy to “git pull” and then “git checkout
> tags/log4j-api-kotlin-1.2.0-rc2”
>
> Web Site: https://logging.staged.apache.org/log4j/kotlin/index.html
>
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachelogging-1073/
>
> Distribution archives:
> https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/
>
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> https://repository.apache.org/content/repositories/orgapachelogging-1073/org/apache/logging/log4j/
>
>  --
> Matt Sicker
>
>

Broken CI

After getting https://github.com/apache/logging-log4j2/pull/646 in what I
think is a good state, I have no idea if it is safe or not to merge because
the 1st build GitHub shows is red:
https://github.com/apache/logging-log4j2/runs/4589771553?check_suite_focus=true

I don't use GH actions the way we do here and I'm not sure why we need the
publish test result set when anyone can just look at the build logs.

Gary

Re: [VOTE] Release Apache Log4j 2.12.3-rc1

Building from the git tag for HEAD detached at log4j-2.12.3-rc1 (2b9359b23)

- mvn apache-rat:check -DskipTests OK
- mvn clean install OK except a JVM crash I always get in the
Cassandra module tests, just like always.
- mvn site -DskipTests fails with:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
project log4j: Error parsing
'/Users/garydgregory/git/logging-log4j-2.12/src/site/xdoc/manual/appenders.xml':
line [1713] Error parsing the model: end tag name  must
match start tag name  from line 1533 (position: TEXT seen
...\n\n... @1713:22)  -> [Help 1]

Is that just me?

Built with:

openjdk version "1.8.0_312"
OpenJDK Runtime Environment (build 1.8.0_312-bre_2021_10_20_23_15-b00)
OpenJDK 64-Bit Server VM (build 25.312-b00, mixed mode)

Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /usr/local/Cellar/maven/3.8.4/libexec
Java version: 1.8.0_312, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@8/1.8.0+312/libexec/openjdk.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "12.1", arch: "x86_64", family: "mac"

Darwin *** 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54
PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64 x86_64

Gary

On Mon, Dec 20, 2021 at 7:52 PM Ralph Goers  wrote:
>
> This is a vote to release Log4j 2.12.3, a security release for Java 7 users.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
>
> The vote will remain open for as short amount as time as required to vet the 
> release. All votes are welcome and we encourage everyone to test the release, 
> but only Logging PMC votes are “officially” counted. As always, at least 3 +1 
> votes and more positive than negative votes are required.
>
> Changes in this version include:
>
> Fixed Bugs
>
> • LOG4J2-3230: Fix string substitution recursion.
> • LOG4J2-3242: Limit JNDI to the java protocol only. JNDI will remain 
> disabled by default. Rename JNDI enablement property from 'log4j2.enableJndi' 
> to 'log4j2.enableJndiLookup', 'log4j2.enableJndiJms', and 
> 'log4j2.enableJndiContextSelector’.
> • LOG4J2-2819: Add support for specifying an SSL configuration for 
> SmtpAppender
>
> Tag:
> a)  for a new copy do "git clone 
> https://github.com/apache/logging-log4j2.git"; and then "git checkout 
> tags/log4j-2.12.3-rc1”  or just "git clone -b log4j-2.12.3-rc1 
> https://github.com/apache/logging-log4j2.git";
> b) for an existing working copy to “git pull” and then “git checkout 
> tags/log4j-2.12.3-rc1”
>
> Web Site:  https://logging.staged.apache.org/log4j/log4j-2.12.3/index.html
>
> Maven Artifacts: 
> https://repository.apache.org/content/repositories/orgapachelogging-1074
>
> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/
>
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate 
> https://repository.apache.org/content/repositories/orgapachelogging-1074/org/apache/logging/log4j/.

[VOTE] Release Apache Log4j 2.12.3-rc1

This is a vote to release Log4j 2.12.3, a security release for Java 7 users.

Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...

Changes in this version include:

Fixed Bugs

• LOG4J2-3230: Fix string substitution recursion.
• LOG4J2-3242: Limit JNDI to the java protocol only. JNDI will remain
disabled by default. Rename JNDI enablement property from 'log4j2.enableJndi'
to 'log4j2.enableJndiLookup', 'log4j2.enableJndiJms', and
'log4j2.enableJndiContextSelector’.
• LOG4J2-2819: Add support for specifying an SSL configuration for
SmtpAppender

Tag:
a) for a new copy do "git clone https://github.com/apache/logging-log4j2.git";
and then "git checkout tags/log4j-2.12.3-rc1” or just "git clone -b
log4j-2.12.3-rc1 https://github.com/apache/logging-log4j2.git";
b) for an existing working copy to “git pull” and then “git checkout
tags/log4j-2.12.3-rc1”

Web Site: https://logging.staged.apache.org/log4j/log4j-2.12.3/index.html

Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachelogging-1074

Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/

Re: Couldn't build release branch without reverting the 2.17.1-SNAPSHOT naming commit

You need to run "mvn install" to get the build to work properly
locally. This is due to some overlapping Maven hackery to bundle Java
9+ code back into the Java 8 code.

On Mon, Dec 20, 2021 at 4:00 PM Dan Kegel  wrote:
>
> I guess this is expected, but on my 2nd machine, I couldn't build the
> release branch because it couldn't find 2.17.1-SNAPSHOT stuff:
>
> [ERROR] Failed to execute goal on project log4j-1.2-api: Could not
> resolve dependencies for project
> org.apache.logging.log4j:log4j-1.2-api:jar:2.17.1-SNAPSHOT:
> org.apache.logging.log4j:log4j-core:jar:tests:2.17.1-SNAPSHOT was not
> found in https://repository.apache.org/snapshots during a previous
> attempt.
>
> After I locally reverted
> https://github.com/apache/logging-log4j2/commit/461dbf25944317de2e689bf6ab2eeb932f143bd4,
> it built ok.
>
> *shrug*
> - Dan

Couldn't build release branch without reverting the 2.17.1-SNAPSHOT naming commit

2021-12-20 Thread Dan Kegel

I guess this is expected, but on my 2nd machine, I couldn't build the
release branch because it couldn't find 2.17.1-SNAPSHOT stuff:

[ERROR] Failed to execute goal on project log4j-1.2-api: Could not
resolve dependencies for project
org.apache.logging.log4j:log4j-1.2-api:jar:2.17.1-SNAPSHOT:
org.apache.logging.log4j:log4j-core:jar:tests:2.17.1-SNAPSHOT was not
found in https://repository.apache.org/snapshots during a previous
attempt.

After I locally reverted
https://github.com/apache/logging-log4j2/commit/461dbf25944317de2e689bf6ab2eeb932f143bd4,
it built ok.

*shrug*
- Dan

Re: Configuration element for system properties

It is not a typo. We may be missing documentation. I’ll have to search and see.

Ralph

> On Dec 20, 2021, at 1:18 PM, Gary Gregory  wrote:
> 
> Our page 
> https://logging.apache.org/log4j/2.x/manual/configuration.html#SystemProperties
> documents log4j2.component.properties, but you talk about
> log4j2.system.properties. Is that a typo or are we missing
> documentation?
> 
> Gary
> 
> On Mon, Dec 20, 2021 at 3:12 PM Ralph Goers  
> wrote:
>> 
>> This proposal is problematic. By the time this happens it is possible it is 
>> too late for some system properties to do any good.
>> 
>> I implemented support for system properties already. I had a need for it for 
>> the Spring support. Just put the properties in log4j2.system.properties.
>> 
>> PropertiesUtil populates the SystemProperties when it creates the 
>> Environment.
>> 
>> Ralph
>> 
>>> On Dec 20, 2021, at 12:18 PM, Gary Gregory  wrote:
>>> 
>>> Hello,
>>> 
>>> I'd like to propose that we add an element called SystemProperty to
>>> our configuration. This would look like our current Property element
>>> but would set a system property instead of a configuration property.
>>> 
>>> My use case is, at work, our tooling generates one XML configuration
>>> file for a user's project and additional XML files for each DTAP
>>> environment. The main Log4j configuration file uses XInclude to bring
>>> in the appropriate DTAP file. Depending on the configuration of the
>>> user's project, and in light of Log4j's use of system properties,
>>> specifically, our new enableJndi* system properties, it would be nice
>>> to be able to say in DTAP XML files something like >> key="enableJndiJms>true or whatever Property
>>> supports.
>>> 
>>> Thoughts?
>>> 
>>> Gary
>>> 
>> 
>

Re: Configuration element for system properties

Our page 
https://logging.apache.org/log4j/2.x/manual/configuration.html#SystemProperties
documents log4j2.component.properties, but you talk about
log4j2.system.properties. Is that a typo or are we missing
documentation?

Gary

On Mon, Dec 20, 2021 at 3:12 PM Ralph Goers  wrote:
>
> This proposal is problematic. By the time this happens it is possible it is 
> too late for some system properties to do any good.
>
> I implemented support for system properties already. I had a need for it for 
> the Spring support. Just put the properties in log4j2.system.properties.
>
> PropertiesUtil populates the SystemProperties when it creates the Environment.
>
> Ralph
>
> > On Dec 20, 2021, at 12:18 PM, Gary Gregory  wrote:
> >
> > Hello,
> >
> > I'd like to propose that we add an element called SystemProperty to
> > our configuration. This would look like our current Property element
> > but would set a system property instead of a configuration property.
> >
> > My use case is, at work, our tooling generates one XML configuration
> > file for a user's project and additional XML files for each DTAP
> > environment. The main Log4j configuration file uses XInclude to bring
> > in the appropriate DTAP file. Depending on the configuration of the
> > user's project, and in light of Log4j's use of system properties,
> > specifically, our new enableJndi* system properties, it would be nice
> > to be able to say in DTAP XML files something like  > key="enableJndiJms>true or whatever Property
> > supports.
> >
> > Thoughts?
> >
> > Gary
> >
>

Re: Configuration element for system properties