Re: (logging-log4j2) branch 2.x updated: Disable PTS on a per-module basis

[Gary D. Gregory]

On 2024/06/14 20:37:44 "Piotr P. Karwasz" wrote:
> Hi Gary,
> 
> On Fri, 14 Jun 2024 at 18:12, Gary Gregory  wrote:
> > I sure hope that all tests are ALWAYS run by default in the 2.x branch,
> > otherwise it will be a -1 from me.
> 
> Currently Predictive Test Selection is enabled on all CI builds,
> except the `release/*` branches, since I am trying to evaluate the
> feature, before I make a proposal on this mailing list. So please,
> indulge me, for a couple of weeks.
> 
> Currently the usage of Develocity is experimental and `logging-log4j2`
> is running builds using the `develocity` branch of `logging-parent`,
> so be reassured that before we do any release:
> 
> 1. We'll largely discuss my findings (PMC meeting in a week or two?),
> 2. `logging-parent` needs to be released.
> 
> For those that have never heard about Develocity, it is a new Gradle
> product that aims at increasing developer productivity by reducing the
> time we wait for our builds to complete.
> INFRA rolled out an ASF instance of Develocity and you can check it out at:
> 
>   
> https://ge.apache.org/scans?search.rootProjectNames=*log4j*=Europe%2FWarsaw#
> 
> I am experimenting with this tool to improve the quality of our test
> suites (aka the code users never help us with). It has some useful
> features like:
> 
> 1. Test execution statistics, which help us identify the broken and
> flaky tests. As it turns out `JeroMqAppenderTest` is not the test that
> fails most often and we also have flaky tests that never (as far as I
> can remember) caused a build to fail. For example `BurstFilterTest`
> fails at least once in 50% of the builds.
> 2. PTS will allow our CI to run faster, because it only runs the tests
> that are more likely to fail for a given code modification. This might
> help contributors that submit PRs to get faster feedback or run the
> test suite before submitting a patch.
> Truth be told, I often skipped the local test run, since it took over
> 30 minutes on my old laptop. On my new desktop I always run all tests,
> since it takes 3 minutes (half of that time Maven is waiting for the 3
> broken Flume tests).
> 
> Of course I have my reservation regarding this tool:
> 
> 1. The Maven plugin it uses is not Open Source. It is probably high
> quality code, but not **provably** high quality code.
> 2. It uses build caching, which might fake the results of builds.
> 
> As far as I understand Develocity should be a no-op on your computers,
> unless you generate an API key for it. If you want to try it, run:
> 
> ./mvnw com.gradle:develocity-maven-extension:provision-access-key
> 
> in a working tree of `logging-log4j2`.

What does that mean, "in a working tree of `logging-log4j2`"? 

I am -1 on changing our PRODUCTION 2.x build. If you want to experiment with 
some company's product, please do so in a non-production branch. The cynic in 
me sees this as a company wanting free advertising to say Apache uses their foo 
product in production.

> 1. The Maven plugin it uses is not Open Source. It is probably high
> quality code, but not **provably** high quality code.
> 2. It uses build caching, which might fake the results of builds.

Well, that sounds horrible: "which might fake the results of builds."

Gary


> 
> Piotr
> 

Re: [VOTE] Release Apache Log4j Tools `0.9.0` RC2

[Gary D. Gregory]

+1

Using the instructions below and

Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /mnt/c/java/apache-maven-3.9.6
Java version: 17.0.10, vendor: Private Build, runtime: 
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.15.133.1-microsoft-standard-wsl2", arch: "amd64", 
family: "unix"

openjdk 17.0.10 2024-01-16
OpenJDK Runtime Environment (build 17.0.10+7-Ubuntu-122.04.1)
OpenJDK 64-Bit Server VM (build 17.0.10+7-Ubuntu-122.04.1, mixed mode, sharing)

Linux RS-PF3NRMLR 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Gary

On 2024/05/09 12:40:32 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools `0.9.0` RC2.
> 
> Website: https://logging.staged.apache.org/log4j/tools-0.9.0
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: 485e1823cd6f8ae581071e938608db21126a7af5
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1285
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 48 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> == Review kit
> 
> The minimum set of steps needed to review the uploaded distribution
> files in the Subversion repository can be summarized as follows:
> 
> # Check out the distribution
> svn co https://dist.apache.org/repos/dist/dev/logging/log4j-tools/0.9.0
> && cd $_
> 
> # Verify checksums
> shasum --check *.sha512
> 
> # Verify signatures
> wget -O - https://downloads.apache.org/logging/KEYS | gpg --import
> for sigFile in *.asc; do gpg --verify $sigFile; done
> 
> # Verify reproduciblity
> umask 0022
> unzip *-src.zip -d src
> cd src
> export 
> NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1285
> sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO
> # If preferred, augment `mvnw` with `-DskipTests` to speed things up
> 
> == Addendum
> 
> Note that the vote period is 48 hours – 24 hours have already passed
> since RC1 vote and there is only a single new commit added, see issue
> #123.
> 
> == Release notes
> 
> This minor release contains small bug fixes and improvements.
> 
> === Added
> 
> * Add `skip` parameter to all Maven goals (#121)
> * Support multiple index and type templates in the
> `log4j-docgen:generate-documentation` configuration (#122)
> * Add support for the `@PluginValue` annotation (#123)
> 
> === Changed
> 
> * Website is migrated to Antora (apache/logging-log4j2#2443)
> 
> === Fixed
> 
> * Fix handling of subclassed plugins in Log4j Docgen (#120)
> 
> === Updated
> 
> * Update `commons-io:commons-io` to version `2.16.1` (#114)
> * Update `org.apache.logging:logging-parent` to version `11.0.0` (#115)
> * Update `org.apache.maven.plugin-tools:maven-plugin-annotations` to
> version `3.13.0` (#118)
> * Update `org.codehaus.modello:modello-maven-plugin` to version `2.4.0` (#119)
> * Update `org.xmlunit:xmlunit-assertj3` to version `2.10.0` (#116)
> 

Re: [VOTE] Release Apache Log4j Tools `0.9.0` RC2

[Gary D. Gregory]

Hi,

Nit:

svn co https://dist.apache.org/repos/dist/dev/logging/log4j-tools/0.9.0 && cd $_

Does not work 100% because $_ evaluates to:

-bash: cd: https://dist.apache.org/repos/dist/dev/logging/log4j-tools/0.9.0: No 
such file or directory

Using: 
Linux RS-PF3NRMLR 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

GG

On 2024/05/09 12:40:32 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools `0.9.0` RC2.
> 
> Website: https://logging.staged.apache.org/log4j/tools-0.9.0
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: 485e1823cd6f8ae581071e938608db21126a7af5
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1285
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 48 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> == Review kit
> 
> The minimum set of steps needed to review the uploaded distribution
> files in the Subversion repository can be summarized as follows:
> 
> # Check out the distribution
> svn co https://dist.apache.org/repos/dist/dev/logging/log4j-tools/0.9.0
> && cd $_
> 
> # Verify checksums
> shasum --check *.sha512
> 
> # Verify signatures
> wget -O - https://downloads.apache.org/logging/KEYS | gpg --import
> for sigFile in *.asc; do gpg --verify $sigFile; done
> 
> # Verify reproduciblity
> umask 0022
> unzip *-src.zip -d src
> cd src
> export 
> NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1285
> sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO
> # If preferred, augment `mvnw` with `-DskipTests` to speed things up
> 
> == Addendum
> 
> Note that the vote period is 48 hours – 24 hours have already passed
> since RC1 vote and there is only a single new commit added, see issue
> #123.
> 
> == Release notes
> 
> This minor release contains small bug fixes and improvements.
> 
> === Added
> 
> * Add `skip` parameter to all Maven goals (#121)
> * Support multiple index and type templates in the
> `log4j-docgen:generate-documentation` configuration (#122)
> * Add support for the `@PluginValue` annotation (#123)
> 
> === Changed
> 
> * Website is migrated to Antora (apache/logging-log4j2#2443)
> 
> === Fixed
> 
> * Fix handling of subclassed plugins in Log4j Docgen (#120)
> 
> === Updated
> 
> * Update `commons-io:commons-io` to version `2.16.1` (#114)
> * Update `org.apache.logging:logging-parent` to version `11.0.0` (#115)
> * Update `org.apache.maven.plugin-tools:maven-plugin-annotations` to
> version `3.13.0` (#118)
> * Update `org.codehaus.modello:modello-maven-plugin` to version `2.4.0` (#119)
> * Update `org.xmlunit:xmlunit-assertj3` to version `2.10.0` (#116)
> 

Re: [Log4j] In 2.x, drop log4j-mongodb3 and add log4j-mongodb5

[Gary D. Gregory]

TY for your help Piotr.

The PR for the 2.x part is here 
https://github.com/apache/logging-log4j2/pull/2486

Gary

On 2024/04/18 02:58:39 "Gary D. Gregory" wrote:
> Hi Piotr, 
> 
> Please see the branch feature/2.x/mongodb-next and its failing tests.
> 
> TY,
> Gary
> 
> On 2024/04/17 21:59:45 "Gary D. Gregory" wrote:
> > This is the plan that Piotr and I came up with one addition (1c):
> > 
> > 1. Branch 2.x
> > 1.a. Drop module log4j-mongodb3
> > 1.b. Add module log4j-mongodb (no number) that contains one class that 
> > instantiates the log4j-mongodb4 provider. XML element is MongoDb.
> > 1.c. Deprecate module log4j-mongodb4 in favor of log4j-mongodb
> > 
> > 2. Branch main
> > 2.a. Rename module log4j-mongodb4 to module log4j-mongodb 
> > 2.b. Rename XML element MongoDb4 to MongoDb
> > 
> > Gary
> > 
> > On 2024/04/17 19:49:40 "Piotr P. Karwasz" wrote:
> > > Hi Gary,
> > > 
> > > On Wed, 17 Apr 2024 at 21:23, Gary Gregory  wrote:
> > > > But then your config has to say  AND depend on the mongodb5
> > > > module! Still confusing 
> > > 
> > > There is actually a rarely used feature of our plugin system, where a
> > > plugin named `Foo` can actually create an object of type `Bar`. See
> > > for example the `LoggerConfig.Root` plugin that actually creates an
> > > object of type `LoggerConfig`.
> > > 
> > > In your config you will use `MongoDb5`, but the provider will be of
> > > type MongoDb4Provider.
> > > 
> > > Piotr
> > > 
> > 
> 

Re: [Log4j] In 2.x, drop log4j-mongodb3 and add log4j-mongodb5

[Gary D. Gregory]

Hi Piotr, 

Please see the branch feature/2.x/mongodb-next and its failing tests.

TY,
Gary

On 2024/04/17 21:59:45 "Gary D. Gregory" wrote:
> This is the plan that Piotr and I came up with one addition (1c):
> 
> 1. Branch 2.x
> 1.a. Drop module log4j-mongodb3
> 1.b. Add module log4j-mongodb (no number) that contains one class that 
> instantiates the log4j-mongodb4 provider. XML element is MongoDb.
> 1.c. Deprecate module log4j-mongodb4 in favor of log4j-mongodb
> 
> 2. Branch main
> 2.a. Rename module log4j-mongodb4 to module log4j-mongodb 
> 2.b. Rename XML element MongoDb4 to MongoDb
> 
> Gary
> 
> On 2024/04/17 19:49:40 "Piotr P. Karwasz" wrote:
> > Hi Gary,
> > 
> > On Wed, 17 Apr 2024 at 21:23, Gary Gregory  wrote:
> > > But then your config has to say  AND depend on the mongodb5
> > > module! Still confusing 
> > 
> > There is actually a rarely used feature of our plugin system, where a
> > plugin named `Foo` can actually create an object of type `Bar`. See
> > for example the `LoggerConfig.Root` plugin that actually creates an
> > object of type `LoggerConfig`.
> > 
> > In your config you will use `MongoDb5`, but the provider will be of
> > type MongoDb4Provider.
> > 
> > Piotr
> > 
> 

Re: [Log4j] In 2.x, drop log4j-mongodb3 and add log4j-mongodb5

[Gary D. Gregory]

This is the plan that Piotr and I came up with one addition (1c):

1. Branch 2.x
1.a. Drop module log4j-mongodb3
1.b. Add module log4j-mongodb (no number) that contains one class that 
instantiates the log4j-mongodb4 provider. XML element is MongoDb.
1.c. Deprecate module log4j-mongodb4 in favor of log4j-mongodb

2. Branch main
2.a. Rename module log4j-mongodb4 to module log4j-mongodb 
2.b. Rename XML element MongoDb4 to MongoDb

Gary

On 2024/04/17 19:49:40 "Piotr P. Karwasz" wrote:
> Hi Gary,
> 
> On Wed, 17 Apr 2024 at 21:23, Gary Gregory  wrote:
> > But then your config has to say  AND depend on the mongodb5
> > module! Still confusing 
> 
> There is actually a rarely used feature of our plugin system, where a
> plugin named `Foo` can actually create an object of type `Bar`. See
> for example the `LoggerConfig.Root` plugin that actually creates an
> object of type `LoggerConfig`.
> 
> In your config you will use `MongoDb5`, but the provider will be of
> type MongoDb4Provider.
> 
> Piotr
> 

[Log4j] In 2.x, drop log4j-mongodb3 and add log4j-mongodb5

[Gary D. Gregory]

Hello All,

In In 2.x, I would like to:

- drop log4j-mongodb3 and
- add log4j-mongodb5
- then do the same in 3.x

Any objections?

Gary

Better Javadoc/Impl for org.apache.logging.log4j.core.Layout.getContentType()

[Gary D. Gregory]

Hi All,

Our current Javadoc says:

/**
 * Returns the content type output by this layout. The base class returns 
"text/plain".
 *
 * @return the content type.
 */
String getContentType();

I'd like to clarify if returning null should be legal/allowed for 
implementation in general.

IOW, I'd like to say either:
- Call sites should be expected to handle null, or
- Implementations MUST not return null

WDYT?
Gary

Re: [VOTE] Release Apache Log4Net 2.0.17

[Gary D. Gregory]

We might need better build instructions... for me at least ;-)

I take it the build.cmd file should be removed since it's not mentioned in 
https://github.com/apache/logging-log4net/blob/master/doc/BUILDING.md ?

BUILDING.md  contains a section called "TL;DR (!Windows):" which is too easy to 
confuse with "TL;DR (Windows):", just say "TL;DR (non-Windows):", there is no 
need to be clever here IMO.

When I say "npm i" and then "npm run build", it starts with:

> log4net@2.0.12 prebuild
> run-s clean-build
> log4net@2.0.12 clean-build
> rimraf build
> log4net@2.0.12 build
> zarro @

Why does it say log4net@2.0.12 when I am building 2.0.17?

Then the build errors out with https://paste.apache.org/1ropz

I, off course, don't know what I'm doing with .net... ;-)

Gary


On 2024/03/15 12:28:03 Davyd McColl wrote:
> Hi all,
> 
> This is a vote to release the Apache Log4net 2.0.17.
> 
> Website: 
> https://logging.staged.apache.org/log4net/release/release-notes.html
> GitHub: https://github.com/apache/logging-log4net
> GitHub release (pre-release): 
> https://github.com/apache/logging-log4net/releases/tag/rel/2.0.17-rc1
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted.
> 
> 
> Thanks to Jan for basically doing all of this (:
> 
> -d
> 
> 

Re: [VOTE] Release Apache Log4Net 2.0.17

[Gary D. Gregory]

Hi and thank you for RM'ing this release.

> https://github.com/apache/logging-log4net/releases/tag/rel/2.0.17-rc1

This is no good IMO, you should provide an _apache_ link.

Gary

On 2024/03/15 12:28:03 Davyd McColl wrote:
> Hi all,
> 
> This is a vote to release the Apache Log4net 2.0.17.
> 
> Website: 
> https://logging.staged.apache.org/log4net/release/release-notes.html
> GitHub: https://github.com/apache/logging-log4net
> GitHub release (pre-release): 
> https://github.com/apache/logging-log4net/releases/tag/rel/2.0.17-rc1
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted.
> 
> 
> Thanks to Jan for basically doing all of this (:
> 
> -d
> 
> 

Re: [VOTE] Release Apache Log4net 2.0.16

[Gary D. Gregory]

I've failed to build probably because the machine I am doing this on is DNS 
locked down for security and can only access certain sites.

I was able to install install-dotnet-core-sdk-1.1.ps1 but not 
install-net-framework-sdk-3.5.ps1 (Error 0x800F0954 in a dialog that points to 
https://learn.microsoft.com/en-US/troubleshoot/windows-client/application-management/dotnet-framework-35-installation-error)
 but I also don't know if how if this machine has enough already on top of 
Microsoft Windows [Version 10.0.19045.4046]

My results: https://paste.apache.org/jj3c8

I rebooted and tried again with the same results.

Gary

On 2024/03/07 03:11:22 Robert Middleton wrote:
> +1
> 
> Verified the following:
> * apache-log4net-source-2.0.16.zip and associated sha/signature
> * apache-log4net-binaries-2.0.16.zip and associated sha/signature
> 
> It looks all good to me.
> 
> -Robert Middleton
> 
> On Tue, Mar 5, 2024 at 1:20 AM Ralph Goers  wrote:
> >
> > +1
> >
> > Verified signatures
> > Verified hashes
> > Verified License and Notice files.
> >
> > Note - the copyright year should be the first year the code was created. 
> > You can update it to include “-(currentYear}” but that is not strictly 
> > necessary.
> >
> > Ralph
> >
> > > On Mar 4, 2024, at 10:48 AM, Jan Friedrich  wrote:
> > >
> > > +1
> > >
> > > Unit tests on my machine were successful.
> > > We integrated the new version into our test environment and all manual 
> > > tests were successful.
> > >
> > > Jan
> > >
> > >> +1
> > >
> > >> Verified signatures.
> > >> Verified hashes.
> > >
> > >> `NOTICE` contains 2022 as the copyright year, but I don't find it a
> > >> blocker. (I have fixed it in `master`.)
> > >
> > >> On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl  wrote:
> > >
> > >>> Hi all
> > >>>
> > >>>
> > >>> This is the vote to release Apache log4net version 2.0.16
> > >>>
> > >>>
> > >>> Website:
> > >>> https://logging.staged.apache.org/log4net/release/release-notes.html
> > >>>
> > >>> GitHub: https://github.com/apache/logging-log4net
> > >>>
> > >>> GitHub release (pre-release):
> > >>> https://github.com/apache/logging-log4net/releases/tag/2.0.16-rc1
> > >>>
> > >>> Distribution: I'm not sure -
> > >>> https://dist.apache.org/repos/dist/dev/logging/log4net should have
> > >>> 2.0.16 binaries and source (I've added via SVN), but I'm not seeing
> > >>> them. Any help appreciated.
> > >>>
> > >>>
> > >>>
> > >>> Please have a look at the staging site & artifacts and test (if you can
> > >>> - clone, `npm i`, `npm test`)
> > >>>
> > >>> [ ] +1, release the artifacts
> > >>>
> > >>> [ ] -1, don't release, because
> > >>>
> > >>>
> > >>> (thanks Piotr: I copied most of your last VOTE mail!)
> > >>>
> > >>>
> > >>> -d
> > >>>
> > >>>
> > >
> >
> 

Re: [log4j] `2.23.1` reproducibility failure (Was: [VOTE] Release Apache Log4j 2.23.1)

[Gary D. Gregory]

And thank you Volkan for walking me through fixing my local issue.

Gary

On 2024/03/06 16:22:50 Gary Gregory wrote:
> The build was completed successfully.
> 
> Gary
> 
> On Wed, Mar 6, 2024 at 11:02 AM Gary Gregory  wrote:
> >
> > I nuked the whole thing (rm -rf ~/.m2/repository/) for good measure
> > (I'll do that once a month from now on).
> >
> > Building (and downloading the world)...
> >
> > It's made it past log4j-bom so we might be looking good...
> >
> > TY!
> > Gary
> >
> > On Wed, Mar 6, 2024 at 10:33 AM Volkan Yazıcı  wrote:
> > >
> > > Could you do `rm -rf ~/.m2/repository/org/apache/commons` and retry,
> > > please? (If you compare `target/bom.xml`s you can see that your local
> > > `commons-*` clones have different hashes.)
> > >
> > > On Wed, Mar 6, 2024 at 4:00 PM Gary Gregory  
> > > wrote:
> > >
> > > > On Wed, Mar 6, 2024 at 9:54 AM Volkan Yazıcı  wrote:
> > > > >
> > > > > Could you share the `target/bom.xml` and
> > > >
> > > > https://paste.apache.org/za0k3
> > > >
> > > > > `target/log4j-bom-2.23.1.buildinfo` files too, please?
> > > >
> > > > https://paste.apache.org/1403q
> > > >
> > > > Gary
> > > >
> > > > >
> > > > > On Wed, Mar 6, 2024 at 3:35 PM Gary Gregory 
> > > > wrote:
> > > > >
> > > > > > rm -rf ~/.m2/repository/org/apache/logging/log4j/*/2.23.1*
> > > > > > export NEXUS_REPO=
> > > > > >
> > > > https://repository.apache.org/content/repositories/orgapachelogging-1261
> > > > > > sh mvnw -Prelease verify artifact:compare 
> > > > > > -Dreference.repo=$NEXUS_REPO
> > > > > >
> > > > > > Gary
> > > > > >
> > > > > > On Wed, Mar 6, 2024 at 9:33 AM Volkan Yazıcı  wrote:
> > > > > > >
> > > > > > > Which command are you exactly running?
> > > > > > >
> > > > > > > Could you share the `target/bom.xml` and
> > > > > > `target/log4j-bom-2.23.1.buildinfo` files too, please?
> > > > > > >
> > > > > > > On Wed, Mar 6, 2024 at 3:28 PM Gary Gregory 
> > > > > > > 
> > > > > > wrote:
> > > > > > >>
> > > > > > >> Same :-(
> > > > > > >>
> > > > > > >> [INFO] --- bnd-baseline:7.0.0:baseline (check-api-compat) @
> > > > log4j-bom
> > > > > > ---
> > > > > > >> [INFO] skip project with packaging=pom
> > > > > > >> [INFO]
> > > > > > >> [INFO] --- artifact:3.5.0:compare (default-cli) @ log4j-bom ---
> > > > > > >> [ERROR] project.build.outputTimestamp property should not be
> > > > inherited
> > > > > > >> but defined in POM
> > > > /Users/garydgregory/rc/log4j/src/.flattened-pom.xml
> > > > > > >> Downloading from reference:
> > > > > > >>
> > > > > >
> > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1.buildinfo
> > > > > > >> [INFO] Reference buildinfo file not found: it will be generated 
> > > > > > >> from
> > > > > > >> downloaded reference artifacts
> > > > > > >> Downloading from reference:
> > > > > > >>
> > > > > >
> > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1.pom
> > > > > > >> Downloaded from reference:
> > > > > > >>
> > > > > >
> > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1.pom
> > > > > > >> (12 kB at 77 kB/s)
> > > > > > >> Downloading from reference:
> > > > > > >>
> > > > > >
> > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1-cyclonedx.xml
> > > > > > >> Downloaded from reference:
> > > > > > >>
> > > > > >
> > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1-cyclonedx.xml
> > > > > > >> (704 kB at 914 kB/s)
> > > > > > >> [INFO] Minimal buildinfo generated from downloaded artifacts:
> > > > > > >>
> > > > > >
> > > > /Users/garydgregory/rc/log4j/src/target/reference/log4j-bom-2.23.1.buildinfo
> > > > > > >> [ERROR] sha512 mismatch log4j-bom-2.23.1-cyclonedx.xml: 
> > > > > > >> investigate
> > > > > > >> with diffoscope
> > > > > > >>
> > > > target/reference/org.apache.logging.log4j/log4j-bom-2.23.1-cyclonedx.xml
> > > > > > >> target/bom.xml
> > > > > > >> [ERROR] Reproducible Build output summary: 1 files ok, 1 
> > > > > > >> different
> > > > > > >> [ERROR] see diff target/reference/log4j-bom-2.23.1.buildinfo
> > > > > > >> target/log4j-bom-2.23.1.buildinfo
> > > > > > >> [ERROR] see also
> > > > > > >> https://maven.apache.org/guides/mini/guide-reproducible-builds.html
> > > > > > >> [INFO] Reproducible Build output comparison saved to
> > > > > > >>
> > > > /Users/garydgregory/rc/log4j/src/target/log4j-bom-2.23.1.buildcompare
> > > > > > >> [INFO] Aggregate buildcompare copied to
> > > > > > >>
> > > > /Users/garydgregory/rc/log4j/src/target/log4j-bom-2.23.1.buildcompare
> > > > > > >> [INFO]
> > > > > >
> > > > 
> > > > > > >> [INFO] Reactor 

[Log4j] If and how to document potential OOME

[Gary D. Gregory]

Hi All,

I'd like to ask how to if we can devise advice around an issue I ran into this 
week.

One of our test suites processes about 40K files of test fixtures. These inputs 
are parsed, processed, and asserted. This randomly fails on a call to 
Logger#debug(), randomly in that it happens usually once per build, somewhere 
in a logging call. But it usually fails with a call that looks like this:

logger.debug("This is fun" + myFunObject);

To simplify things, let's say that it turns out that after an underlying third 
party jar file version upgrade the call to myFunObject#toString() no longer 
returns Object#toString() but rather (again to simplify) the contents of the 
file that was parsed to create myFunObject. This toString() can be megabytes. 
The solution is obvious:

logger.debug("This is fun", myFunObject::toString)

And our CI builds no longer randomly fail since our default logging does not 
log at the debug level.

A better solution could be:

logger.debug("This is fun", () -> myFunObject.toString().substring(0, 100))

where I still want _some_ information better than making my own toString() with 
System#identityHashCode(Object) or somesuch. Sure, .toString() is still called 
but it does not make it down into logging. In my case the OOME happened in 
myFunObject::toString so the substring() example would not have worked.

My question is: Should we document some general advice on this pattern and what 
should the advice be? Would it make sense to have some features where we 
truncate/reject Strings above a threshold. And yes, calling 
myFunObject.toString() can still still get me in trouble.

Gary

Re: All-in-one site documentation

[Gary D. Gregory]

FYI 
https://cwiki.apache.org/confluence/display/JUNEAU/Adding+content+to+the+overview-summary.html+file

On 2023/12/18 17:37:36 "Gary D. Gregory" wrote:
> Hi All,
> 
> A while back, I mentioned that we could (not should) have our documentation 
> generated within Javadoc. Here is an example from another Apache project I 
> participate in: 
> 
> https://juneau.apache.org/site/apidocs-9.0.1/index.html
> 
> I'm late to Juneau and I don't know the ins and out of how it's made, but it 
> looks good nonetheless IMO.
> 
> Gary
> 

All-in-one site documentation

[Gary D. Gregory]

Hi All,

A while back, I mentioned that we could (not should) have our documentation 
generated within Javadoc. Here is an example from another Apache project I 
participate in: 

https://juneau.apache.org/site/apidocs-9.0.1/index.html

I'm late to Juneau and I don't know the ins and out of how it's made, but it 
looks good nonetheless IMO.

Gary

Re: [VOTE] Release Apache Log4j 2.22.0

[Gary D. Gregory]

Hi,

The only way I could get the build to pass is to let 'mvn clean verify' run 
while I went to lunch and nothing else was running.

I would not in want to vote without running all the tests.

+1

Gary

On 2023/11/17 14:16:14 Volkan Yazıcı wrote:
> File-based tests on Windows are not stable.
> Occasionally they have hiccups.
> Would you mind retrying, please?
> 
> You can speed up the process as follows:
> 
> # Install everything without any checks
> ./mvnw install -DskipTests -Dspotbugs.skip -Dspotless.skip
> 
> # Verify everything except `log4j-core-test`
> ./mvnw verify -pl \!:log4j-core-test
> 
> # Verify only `log4j-core-test`
> ./mvnw verify -pl :log4j-core-test
> 
> On Fri, Nov 17, 2023 at 3:03 PM Gary D. Gregory  wrote:
> >
> > Build failure for me on Windows from the src zip and 'mvn clean verify':
> >
> > [ERROR] Failures:
> > [ERROR]   RollingAppenderDeleteMaxDepthTest.testAppender:73 
> > [target\rolling-with-delete-depth\test\1, 
> > target\rolling-with-delete-depth\test\2, 
> > target\rolling-with-delete-depth\test\test-1.log, 
> > target\rolling-with-delete-depth\test\test-2.log, 
> > target\rolling-with-delete-depth\test\test-3.log, 
> > target\rolling-with-delete-depth\test\test-4.log] expected:<5> but was:<6>
> > [ERROR]   RollingAppenderDeleteScriptTest.testAppender:73 
> > target\rolling-with-delete-script\test\test-2.log should have odd index
> > [ERROR]   
> > AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
> >  [Log file 'AsyncLoggerTest.log']
> > expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
> > configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
> > CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
> >  but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
> > configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
> > CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
> > [ERROR]   
> > AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
> >  [Log file 'AsyncLoggerTest.log']
> > expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
> > configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
> > GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
> >  but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
> > configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
> > GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
> > [ERROR] Errors:
> > [ERROR]   
> > AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
> >  » ConditionTimeout Condition with lambda expression in 
> > org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
> > uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled 
> > within 500 milliseconds.
> > [ERROR]   
> > AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
> >  » ConditionTimeout Condition with lambda expression in 
> > org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
> > uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled 
> > within 500 milliseconds.
> > [INFO]
> > [ERROR] Tests run: 2452, Failures: 4, Errors: 2, Skipped: 35
> >
> > All that I could capture in the console is here: 
> > https://paste.apache.org/k6auj
> >
> > - Testing src zip file
> > - OK: ASC verify
> > - OK SHA check
> > - mvn clean verify
> >
> > Using:
> >
> > Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> > Maven home: C:\java\apache-maven-3.9.5
> > Java version: 11.0.20, vendor: Eclipse Adoptium, runtime: C:\Program 
> > Files\Eclipse Adoptium\jdk-11.0.20.8-hotspot
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> > Microsoft Windows [Version 10.0.19045.3570]
> >
> > Gary
> >
> > On 2023/11/17 12:07:06 Volkan Yazıcı wrote:
> > > This is a vote to release the Apache Log4j 2.22.0.
> > >
> > > Website: https://logging.staged.apache.org/log4j
> > > GitHub: https://github

Re: [VOTE] Release Apache Log4j 2.22.0

[Gary D. Gregory]

Build failure for me on Windows from the src zip and 'mvn clean verify':

[ERROR] Failures:
[ERROR]   RollingAppenderDeleteMaxDepthTest.testAppender:73 
[target\rolling-with-delete-depth\test\1, 
target\rolling-with-delete-depth\test\2, 
target\rolling-with-delete-depth\test\test-1.log, 
target\rolling-with-delete-depth\test\test-2.log, 
target\rolling-with-delete-depth\test\test-3.log, 
target\rolling-with-delete-depth\test\test-4.log] expected:<5> but was:<6>
[ERROR]   RollingAppenderDeleteScriptTest.testAppender:73 
target\rolling-with-delete-script\test\test-2.log should have odd index
[ERROR]   
AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
 [Log file 'AsyncLoggerTest.log']
expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
 but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
[ERROR]   
AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
 [Log file 'AsyncLoggerTest.log']
expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
 but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
[ERROR] Errors:
[ERROR]   
AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
 » ConditionTimeout Condition with lambda expression in 
org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled within 
500 milliseconds.
[ERROR]   
AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
 » ConditionTimeout Condition with lambda expression in 
org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled within 
500 milliseconds.
[INFO]
[ERROR] Tests run: 2452, Failures: 4, Errors: 2, Skipped: 35

All that I could capture in the console is here: https://paste.apache.org/k6auj

- Testing src zip file
- OK: ASC verify
- OK SHA check
- mvn clean verify

Using:

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: C:\java\apache-maven-3.9.5
Java version: 11.0.20, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-11.0.20.8-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Microsoft Windows [Version 10.0.19045.3570]

Gary

On 2023/11/17 12:07:06 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j 2.22.0.
> 
> Website: https://logging.staged.apache.org/log4j
> GitHub: https://github.com/apache/logging-log4j2
> Commit: a1634d695e5702ecab505fea5aadaf9890641487
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1238
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted.
> 
> == Review kit
> 
> The minimum set of steps needed to review the uploaded distribution
> files can be summarized as follows:
> 
> # Verify checksums
> shasum --check *.sha512
> 
> # Verify signatures
> for sigFile in *.asc; do gpg --verify $sigFile; done
> 
> # Verify reproduciblity
> umask 0022
> unzip *-src.zip -d src
> cd src
> export 
> NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1238
> sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO
> 
> == Release notes
> 
> This release provides a CycloneDX Software Bill of Materials (SBOM)[1]
> along with each artifact and contains bug fixes addressing issues in
> the JPMS & OSGi infrastructure overhauled in `2.21.0`, dependency
> updates, and some other minor fixes and improvements.
> 
> [1] https://cyclonedx.org/capabilities/sbom
> 
> === CycloneDX Software Bill of Materials (SBOM)
> 
> This is the first Log4j release that provides a CycloneDX 

Re: [VOTE] Release Apache Log4j Tools 0.6.0 (RC2)

[Gary D. Gregory]

+1

Same warnings as noted previously.

- Testing src zip file
- OK: ASC verify
- OK: SHA check
- OK: mvn clean verify

Using:

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: C:\java\apache-maven-3.9.5
Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Microsoft Windows [Version 10.0.19045.3570]

Gary

On 2023/11/17 09:21:48 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools 0.6.0 (RC2).
> 
> Website: https://logging.staged.apache.org/log4j/tools
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: a696e081304cc0693d86533013df5b4d886cfb9c
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1237
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 24 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> === Note on 24 hours deadline
> 
> RC1 vote was created 2 days ago. RC2 only contains missing CycloneDX
> SBOMs in the distribution archived by ASF. Note that SBOMs in the
> Nexus were already working in RC1. Hence, an extra 24 hours would make
> it all add up to 72 hours.
> 
> === Release Notes
> 
> This minor release contains various bug fixes and improvements.
> 
>  Added
> 
> * Started generating CycloneDX SBOM with the recent update of
> `logging-parent` to version `10.4.0`
> 
>  Changed
> 
> * Update `org.apache.logging:logging-parent` to version `10.4.0`
> 
>  Fixed
> 
> * `log4j-tools-bom` was broken due to removed `parent` during
> flattening. This is automatically fixed by the recent `logging-parent`
> version `10.4.0` update.
> 

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Gary D. Gregory]

Also seen during 'mvn clean verify':

[INFO] --- compiler:3.11.0:compile (default-compile) @ 
log4j-changelog-maven-plugin ---
[INFO] Changes detected - recompiling the module! :dependency
[INFO] Compiling 5 source files with javac [debug release 8] to target\classes
[WARNING] Cannot find annotation method 'value()' in type 
'edu.umd.cs.findbugs.annotations.SuppressFBWarnings': class file for 
edu.umd.cs.findbugs.annotations.SuppressFBWarnings not found


Gary

On 2023/11/15 15:03:13 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools 0.6.0.
> 
> Website: https://logging.staged.apache.org/log4j/tools
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: 18425d95a4d150de905929d55bf55545d70f3d91
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1233
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> === Release Notes
> 
> This minor release contains various bug fixes and improvements.
> 
>  Added
> 
> * Started generating CycloneDX SBOM with the recent update of
> `logging-parent` to version `10.4.0`
> 
>  Changed
> 
> * Update `org.apache.logging:logging-parent` to version `10.4.0`
> 
>  Fixed
> 
> * `log4j-tools-bom` was broken due to removed `parent` during
> flattening. This is automatically fixed by the recent `logging-parent`
> version `10.4.0` update.
> 

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Gary D. Gregory]

Seen during 'mvn clean verify'

[INFO] --- log4j-changelog:0.5.0:export (export-changelog) @ log4j-tools-bom ---
[WARNING] The POM for org.apache.logging.log4j:log4j-changelog:jar:0.5.0 is 
invalid, transitive dependencies (if any) will not be available, enable debug 
logging for more details
exported 6 release directories: ..., `C:\tmp\test\src\changelog\0.6.0`
exporting upcoming release directory: `C:\tmp\test\src\changelog\.0.x.x`

Is that important? What doe sit mean?

TY!
Gary


On 2023/11/15 15:03:13 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools 0.6.0.
> 
> Website: https://logging.staged.apache.org/log4j/tools
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: 18425d95a4d150de905929d55bf55545d70f3d91
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1233
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> === Release Notes
> 
> This minor release contains various bug fixes and improvements.
> 
>  Added
> 
> * Started generating CycloneDX SBOM with the recent update of
> `logging-parent` to version `10.4.0`
> 
>  Changed
> 
> * Update `org.apache.logging:logging-parent` to version `10.4.0`
> 
>  Fixed
> 
> * `log4j-tools-bom` was broken due to removed `parent` during
> flattening. This is automatically fixed by the recent `logging-parent`
> version `10.4.0` update.
> 

Re: [VOTE] Release Apache Log4j JMX GUI 2.22.0

[Gary D. Gregory]

+1
- Testing source zip file
- OK: ASC
- OK: SHA
- OK: mvn clean verify
- OK: jar --describe-module --file=log4j-jmx-gui-2.22.0.jar

Using:

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: C:\java\apache-maven-3.9.5
Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Microsoft Windows [Version 10.0.19045.3570]

Gary

On 2023/11/15 15:47:17 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j JMX GUI 2.22.0.
> 
> Website: https://logging.staged.apache.org/log4j/jmx-gui
> GitHub: https://github.com/apache/logging-log4j-jmx-gui
> Commit: a61f686edfd0d5c9591b98b80ebcfb533bebe23e
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-jmx-gui
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1234
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> === Release Notes
> 
> This release contains minor improvements.
> 
> === Added
> 
> * Started generating CycloneDX SBOM with the recent update of
> `logging-parent` to version `10.4.0`
> * Publish the website[1]
> 
> [1] https://logging.apache.org/log4j/jmx-gui
> 
> === Changed
> 
> * Add OSGi and JPMS descriptors
> * Update `log4j-core` to version `2.21.1`
> * Update `logging-parent` to version `10.4.0`
> 
> === Fixed
> 
> * Restore the original Maven `groupId`: `org.apache.logging.log4j`
> 

Re: [VOTE] Deprecation of 2.x modules/features and removal in 3.x

[Gary D. Gregory]

On 2023/11/02 15:05:05 "Piotr P. Karwasz" wrote:
> Hi Gary,
> 
> On Thu, 2 Nov 2023 at 15:42, Gary Gregory  wrote:
> > >  * Jackson based layouts (JsonLayout, XmlLayout, YamlLayout)
> > -1: I want the ability to log to XML (narrow use-case, sure, but handy).
> 
> Does it really need to be Jackson? Jackson is optimized for JSON, we
> can easily write a SAX, StAX or JAXB appender in a couple of hours.

That was not the question asked by this VOTE. Also, smells or NIH and "famous 
last words" ;-)

> 
> > >  * `log4j-spring-boot`:
> > -1: Spring seems too important.
> 
> Are you sure you want to _veto_ a module removal based on a feeling?
> `log4j-spring-boot` has 4 elements: a lookup, a property source, an
> arbiter and an improved version of `Log4j2LoggingSystem`.
> All these elements were submitted to Spring Boot by Ralph and included in 3.x.
> So this module targets the users that don't want Spring Boot 3.x, but
> want Log4j 3.x.

I feel it is too big an ask to force people to migrate to 3.x which is not 
released.

I also feel ALL of this is premature until 3.x is out.

Gary

> 
> Piotr
> 

Re: [ANNOUNCE] Apache Log4j 2.21.1 released

[Gary D. Gregory]

Odd, I do not even see 2.21.1 on 
https://repository.apache.org/content/groups/public/org/apache/logging/log4j/log4j-api/

?

Gary

On 2023/10/24 11:21:01 "Gary D. Gregory" wrote:
> Please do not announce before the jars show up on 
> https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-api/
> 
> TY!
> Gary
> 
> On 2023/10/24 07:06:12 "Piotr P. Karwasz" wrote:
> > Apache Log4j team is pleased to announce the 2.21.1
> > release. Apache Log4j is a versatile, industrial-strength
> > Java logging framework composed of an API, its implementation,
> > and components to assist the deployment for various use cases.
> > For further information (support, download, etc.) see the project
> > website[1].
> > 
> > [1] https://logging.apache.org/log4j
> > 
> > == Release Notes
> > 
> > This patch release contains only the fix of a `log4j-jcl` bug that
> > prevents it from connecting with `commons-logging`.
> > 
> > The Log4j 2.21.1 API, as well as the other artifacts, maintains binary
> > compatibility with the previous release.
> > 
> > Apache Log4j 2.21.1 requires Java 8 to run.
> > The build requires JDK 11 and generates reproducible binaries.
> > 
> > For complete information on Apache Log4j 2, including instructions on
> > how to submit bug reports, patches, get support, or suggestions for
> > improvement, see the Apache Log4j 2.x website[2].
> > 
> > [2] http://logging.apache.org/log4j/2.x/
> > 
> > === Fixed
> > 
> > * Fixes the Apache Commons Logging (JCL) bridge: `log4j-jcl`. (#1865)
> > 
> > Piotr
> > 
> 

Re: [ANNOUNCE] Apache Log4j 2.21.1 released

[Gary D. Gregory]

Please do not announce before the jars show up on 
https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-api/

TY!
Gary

On 2023/10/24 07:06:12 "Piotr P. Karwasz" wrote:
> Apache Log4j team is pleased to announce the 2.21.1
> release. Apache Log4j is a versatile, industrial-strength
> Java logging framework composed of an API, its implementation,
> and components to assist the deployment for various use cases.
> For further information (support, download, etc.) see the project
> website[1].
> 
> [1] https://logging.apache.org/log4j
> 
> == Release Notes
> 
> This patch release contains only the fix of a `log4j-jcl` bug that
> prevents it from connecting with `commons-logging`.
> 
> The Log4j 2.21.1 API, as well as the other artifacts, maintains binary
> compatibility with the previous release.
> 
> Apache Log4j 2.21.1 requires Java 8 to run.
> The build requires JDK 11 and generates reproducible binaries.
> 
> For complete information on Apache Log4j 2, including instructions on
> how to submit bug reports, patches, get support, or suggestions for
> improvement, see the Apache Log4j 2.x website[2].
> 
> [2] http://logging.apache.org/log4j/2.x/
> 
> === Fixed
> 
> * Fixes the Apache Commons Logging (JCL) bridge: `log4j-jcl`. (#1865)
> 
> Piotr
> 

Re: [VOTE] Release Apache Log4j 2.21.1 RC1

[Gary D. Gregory]

Does not matter, running "mvn clean verify -Psequential-tests", I still get:

[ERROR] Failures:
[ERROR]   UrlConnectionFactoryTest.withAuthentication:130 File was not modified 
==> expected: <200> but was: <304>
[INFO]
[ERROR] Tests run: 2774, Failures: 1, Errors: 0, Skipped: 35

Gary

On 2023/10/23 12:50:59 Gary Gregory wrote:
> On Mon, Oct 23, 2023 at 8:10 AM Piotr P. Karwasz
>  wrote:
> >
> > Hi Gary,
> >
> > On Mon, 23 Oct 2023 at 13:33, Gary D. Gregory  wrote:
> > >
> > > I reran again yesterday, got the same 2 failures we know about plus a new 
> > > one:
> >
> > Parallel tests on Windows must be worse than I imagined. Can you run
> > with `-Psequential-tests` in the meantime and I'll try to fix those
> > problems in a future release?
> 
> Testing...
> 
> Gary
> 
> >
> > Piotr
> 

Re: [VOTE] Release Apache Log4j 2.21.1 RC1

[Gary D. Gregory]

I reran again yesterday, got the same 2 failures we know about plus a new one:

[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.236 s 
<<< FAILURE! -- in org.apache.logging.log4j.core.config.FileOutputTest
[ERROR] org.apache.logging.log4j.core.config.FileOutputTest.testConfig -- Time 
elapsed: 5.628 s <<< FAILURE!
org.opentest4j.AssertionFailedError:
target\test.log failed with java.nio.file.FileSystemException: target\test.log: 
The process cannot access the file because it is being used by another process.

at 
org.apache.logging.log4j.test.junit.AbstractFileCleaner.clean(AbstractFileCleaner.java:82)
at 
org.apache.logging.log4j.test.junit.AbstractFileCleaner.beforeEach(AbstractFileCleaner.java:43)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
Suppressed: org.opentest4j.AssertionFailedError: target\test.log failed 
with java.nio.file.FileSystemException: target\test.log: The process cannot 
access the file because it is being used by another process.

at 
org.apache.logging.log4j.test.junit.AbstractFileCleaner.clean(AbstractFileCleaner.java:82)
at 
org.apache.logging.log4j.test.junit.AbstractFileCleaner.afterEach(AbstractFileCleaner.java:48)
... 2 more

at 
org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)

Gary

On 2023/10/21 20:28:31 "Piotr P. Karwasz" wrote:
> Hi Gary,
> 
> On Sat, 21 Oct 2023 at 15:11, Gary D. Gregory  wrote:
> >
> > I got this failure:
> >
> > [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> > 29.00 s <<< FAILURE! -- in 
> > org.apache.logging.log4j.core.net.UrlConnectionFactoryTest
> > [ERROR] 
> > org.apache.logging.log4j.core.net.UrlConnectionFactoryTest.withAuthentication
> >  -- Time elapsed: 0.039 s <<< FAILURE!
> 
> On Sat, 21 Oct 2023 at 15:25, Gary D. Gregory  wrote:
> >
> > Dang, another random failure:
> >
> > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> > 53.21 s <<< FAILURE! -- in 
> > org.apache.logging.log4j.core.appender.rolling.RollingAppenderCronAndSizeTest
> > [ERROR] 
> > org.apache.logging.log4j.core.appender.rolling.RollingAppenderCronAndSizeTest.testAppender
> >  -- Time elapsed: 53.16 s <<< FAILURE!
> 
> I'll look into those. Some tests in a parallel run fail if multiple
> tests access the same file (especially on Windows), but these do not
> seem to match this category.
> 
> Piotr
> 

Re: [VOTE] Release Apache Log4j 2.21.1 RC1

[Gary D. Gregory]

Dang, another random failure:

[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 53.21 s 
<<< FAILURE! -- in 
org.apache.logging.log4j.core.appender.rolling.RollingAppenderCronAndSizeTest
[ERROR] 
org.apache.logging.log4j.core.appender.rolling.RollingAppenderCronAndSizeTest.testAppender
 -- Time elapsed: 53.16 s <<< FAILURE!
org.junit.ComparisonFailure: Incorrect file name. Expected counter value of 1 
in rollingfile_2023-10-21-09-22-33_-1.log expected:<[]1> but was:<[-]1>
at org.junit.Assert.assertEquals(Assert.java:117)
at 
org.apache.logging.log4j.core.appender.rolling.RollingAppenderCronAndSizeTest.testAppender(RollingAppenderCronAndSizeTest.java:90)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.apache.logging.log4j.core.test.junit.LoggerContextRule$1.evaluate(LoggerContextRule.java:126)

My machine is busy doing other things, but it would be nice if the tests could 
be given more time to run because I plan on using my PC and letting this run in 
the background.

Gary


On 2023/10/21 13:11:42 "Gary D. Gregory" wrote:
> I got this failure:
> 
> [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 29.00 
> s <<< FAILURE! -- in 
> org.apache.logging.log4j.core.net.UrlConnectionFactoryTest
> [ERROR] 
> org.apache.logging.log4j.core.net.UrlConnectionFactoryTest.withAuthentication 
> -- Time elapsed: 0.039 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: File was not modified ==> expected: 
> <200> but was: <304>
> at 
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at 
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at 
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at 
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:559)
> at 
> org.apache.logging.log4j.core.net.UrlConnectionFactoryTest.withAuthentication(UrlConnectionFactoryTest.java:130)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
> 
> Running: mvn clean verify
> 
> Using:
> 
> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> Maven home: C:\java\apache-maven-3.9.5
> Java version: 11.0.20, vendor: Eclipse Adoptium, runtime: C:\Program 
> Files\Eclipse Adoptium\jdk-11.0.20.8-hotspot
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> 
> I'll run it again to see if its a random error...
> 
> Gary
> 
> 
> On 2023/10/20 21:20:00 "Piotr P. Karwasz" wrote:
> > This is a vote to release the Apache Log4j 2.21.1.
> > 
> > Website: https://logging-log4j2.staged.apache.org/log4j
> > GitHub: https://github.com/apache/logging-log4j2
> > Commit: e613e9ed71279bb52753a4df810d61c11389df81
> > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j
> > Nexus: 
> > https://repository.apache.org/content/repositories/orgapachelogging-1209
> > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> > 
> > Please download, test, and cast your votes on this mailing list.
> > 
> > [ ] +1, release the artifacts
> > [ ] -1, don't release, because...
> > 
> > This vote is open for 72 hours and will pass unless getting a
> > net negative vote count. All votes are welcome and we encourage
> > everyone to test the release, but only the Logging Services PMC
> > votes are officially counted.
> > 
> > == Countdown
> > 
> > https://www.timeanddate.com/countdown/party?iso=20231023T2320=1449=cursive
> > 
> > == Release Notes
> > 
> > This patch release contains only the fix of a `log4j-jcl` bug that
> > prevents it from connecting with `commons-logging`.
> > 
> > The Log4j 2.21.1 API, as well as the other artifacts, maintains binary
> > compatibility with the previous release.
> > 
> > Apache Log4j 2.21.1 requires Java 8 to run.
> > The build requires JDK 11 and generates reproducible binaries.
> > 
> > For complete information on Apache Log4j 2, including instructions on
> > how to submit bug reports, patches, get support, or suggestions for
> > improvement, see http://logging.apache.org/log4j/2.x/[the Apache Log4j
> > 2 website].
> > 
> > 
> > === Fixed
> > 
> > * Fixes the Apache Commons Logging (JCL) bridge: `log4j-jcl`. (#1865)
> > 
> > Piotr
> > 
> 

Re: [VOTE] Release Apache Log4j 2.21.1 RC1

[Gary D. Gregory]

I got this failure:

[ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 29.00 s 
<<< FAILURE! -- in org.apache.logging.log4j.core.net.UrlConnectionFactoryTest
[ERROR] 
org.apache.logging.log4j.core.net.UrlConnectionFactoryTest.withAuthentication 
-- Time elapsed: 0.039 s <<< FAILURE!
org.opentest4j.AssertionFailedError: File was not modified ==> expected: <200> 
but was: <304>
at 
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at 
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at 
org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at 
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:559)
at 
org.apache.logging.log4j.core.net.UrlConnectionFactoryTest.withAuthentication(UrlConnectionFactoryTest.java:130)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)

Running: mvn clean verify

Using:

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: C:\java\apache-maven-3.9.5
Java version: 11.0.20, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-11.0.20.8-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

I'll run it again to see if its a random error...

Gary


On 2023/10/20 21:20:00 "Piotr P. Karwasz" wrote:
> This is a vote to release the Apache Log4j 2.21.1.
> 
> Website: https://logging-log4j2.staged.apache.org/log4j
> GitHub: https://github.com/apache/logging-log4j2
> Commit: e613e9ed71279bb52753a4df810d61c11389df81
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1209
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted.
> 
> == Countdown
> 
> https://www.timeanddate.com/countdown/party?iso=20231023T2320=1449=cursive
> 
> == Release Notes
> 
> This patch release contains only the fix of a `log4j-jcl` bug that
> prevents it from connecting with `commons-logging`.
> 
> The Log4j 2.21.1 API, as well as the other artifacts, maintains binary
> compatibility with the previous release.
> 
> Apache Log4j 2.21.1 requires Java 8 to run.
> The build requires JDK 11 and generates reproducible binaries.
> 
> For complete information on Apache Log4j 2, including instructions on
> how to submit bug reports, patches, get support, or suggestions for
> improvement, see http://logging.apache.org/log4j/2.x/[the Apache Log4j
> 2 website].
> 
> 
> === Fixed
> 
> * Fixes the Apache Commons Logging (JCL) bridge: `log4j-jcl`. (#1865)
> 
> Piotr
> 

Re: [VOTE] Release Apache Log4j 2.21.0

[Gary D. Gregory]

I just ran mvn clean verify and I think I need a new machine ;-) I took... 13 
hours?

[INFO] Reactor Summary for Apache Log4j BOM 2.21.0:
[INFO]
[INFO] Apache Log4j BOM ... SUCCESS [ 22.553 s]
[INFO] Apache Log4j Parent  SUCCESS [  1.001 s]
[INFO] Apache Log4j API Java 9 support  SUCCESS [ 13.793 s]
[INFO] Apache Log4j API ... SUCCESS [ 17.593 s]
[INFO] Apache Log4j Implementation Java 9 support . SUCCESS [  3.302 s]
[INFO] Apache Log4j Core .. SUCCESS [ 53.174 s]
[INFO] Apache Log4j API Tests . SUCCESS [01:31 min]
[INFO] Apache Log4j Core Tests  SUCCESS [  12:48 h]
[INFO] Apache Log4j 1.x Compatibility API . SUCCESS [01:27 min]
[INFO] Apache Log4j App Server Support  SUCCESS [  3.361 s]
[INFO] Apache Log4j to SLF4J Adapter .. SUCCESS [ 10.116 s]
[INFO] Apache Log4j SLF4J Binding . SUCCESS [ 16.419 s]
[INFO] Apache Log4j Cassandra . SUCCESS [  9.899 s]
[INFO] Apache Log4j Core Integration Tests  SUCCESS [  6.208 s]
[INFO] Apache Log4j CouchDB ... SUCCESS [  3.788 s]
[INFO] Apache Log4j Docker Library  SUCCESS [  3.271 s]
[INFO] Apache Log4j Commons Logging Bridge  SUCCESS [ 21.961 s]
[INFO] Apache Log4j Flume Bridge .. SUCCESS [01:25 min]
[INFO] Apache Log4j Streaming Interface ... SUCCESS [ 23.117 s]
[INFO] Apache Log4j Jakarta SMTP .. SUCCESS [  9.385 s]
[INFO] Apache Log4j Jakarta Web ... SUCCESS [ 13.454 s]
[INFO] Apache Log4j JPA ... SUCCESS [ 24.396 s]
[INFO] Apache Log4j JDK Platform Logging Adapter .. SUCCESS [  7.531 s]
[INFO] Apache Log4j JDBC DBCP 2 ... SUCCESS [  8.388 s]
[INFO] Apache Log4j JUL Adapter ... SUCCESS [ 22.978 s]
[INFO] Apache Log4j Kubernetes Library  SUCCESS [  9.065 s]
[INFO] Apache Log4j JSON Template Layout .. SUCCESS [  8.276 s]
[INFO] Apache Log4j JSON Template Layout tests  SUCCESS [ 46.068 s]
[INFO] Apache Log4j MongoDB 3 . SUCCESS [ 52.379 s]
[INFO] Apache Log4j MongoDB 4 . SUCCESS [ 44.917 s]
[INFO] Apache Log4j to JUL Bridge . SUCCESS [  7.898 s]
[INFO] Apache Log4j OSGi .. SUCCESS [ 12.320 s]
[INFO] Apache Log4J Performance Tests . SUCCESS [ 15.628 s]
[INFO] Apache Log4j SLF4J 2.0 Binding . SUCCESS [ 16.239 s]
[INFO] Apache Log4j Spring Boot Support ... SUCCESS [ 11.931 s]
[INFO] Apache Log4j Spring Cloud Config Support ... SUCCESS [  0.746 s]
[INFO] Apache Log4j Spring Cloud Config Client Support  SUCCESS [ 13.337 s]
[INFO] Apache Log4j Web ... SUCCESS [ 14.779 s]
[INFO] Apache Log4j Tag Library ... SUCCESS [ 15.585 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  13:02 h
[INFO] Finished at: 2023-10-14T00:10:38-04:00
[INFO] 

My machine must have been busy doing something else. Aside from that, I tested 
the src zip file. ASC OK. SHA OK. I also ran a separate RAT check: OK.

+1

Gary


On 2023/10/13 09:08:28 Christian Grobmeier wrote:
> This is a vote to release the Apache Log4j 2.21.0.
> 
> Website: https://logging-log4j.staged.apache.org/log4j/2.x/
> GitHub: https://github.com/apache/logging-log4j2
> Commit: 493d9a9daabc72d10582c4682538baa93a2a
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1202
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted.
> 
> == Release Notes
> 
> This release primarily focuses on enhancements to our OSGi and JPMS support 
> and contains several bug fixes.
> It will be the first release built and signed by the CI using the 
> https://keyserver.ubuntu.com/pks/lookup?search=077E8893A6DCC33DD4A4D5B256E73BA9A0B592D0=index[ASF
>  Logging Services Release Manager GPG key], which is shared in 
> 

Re: [VOTE] Release Apache Log4j JMX GUI 2.21.0 (RC2)

[Gary D. Gregory]

- ASC seems OK. 
- Can't easily mechanically check sha512 but eyeballing it appears OK.
- mvn apache-rat:check OK
- Built OK 'mvn clean verify' 
- Running with 'java -jar target\...jar localhost:333' starts the app and fails 
which is fine since I did not try with an actual app.
- We have ... ZERO unit tests or ITs? Yikes :-(

I'm going +1 just based on the mechanics of building and trust the RM ran an 
app ;-)

Test bed:

Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: C:\java\apache-maven-3.9.4
Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Gary

On 2023/09/15 08:54:45 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j JMX GUI 2.21.0 (RC2).
> 
> Source repository: https://github.com/apache/logging-log4j-jmx-gui
> Commit: c3056b340f57e2d6bd66b9f825722c336090d0d2
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-jmx-gui
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1175
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 24 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> # RC1..RC2 changes
> 
> - Added `Main-Class` to `MANIFEST.MF`
> 
> # Release Notes
> 
> This marks the first release where the Log4j JMX GUI is released
> separately from the Log4j itself.
> 
> ## Changes
> 
> ### Added
> 
> * Project is moved to a new repository[1] with its own release cycle
> 
> [1] https://github.com/apache/logging-log4j-jmx-gui
> 

Re: [VOTE] Release Apache Log4j JMX GUI 2.21.0 (RC2)

[Gary D. Gregory]

Not a blocker but should be fixed IMO: The verify goal does not run 
apache-rat:check

Gary

On 2023/09/15 08:54:45 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j JMX GUI 2.21.0 (RC2).
> 
> Source repository: https://github.com/apache/logging-log4j-jmx-gui
> Commit: c3056b340f57e2d6bd66b9f825722c336090d0d2
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-jmx-gui
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1175
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 24 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> # RC1..RC2 changes
> 
> - Added `Main-Class` to `MANIFEST.MF`
> 
> # Release Notes
> 
> This marks the first release where the Log4j JMX GUI is released
> separately from the Log4j itself.
> 
> ## Changes
> 
> ### Added
> 
> * Project is moved to a new repository[1] with its own release cycle
> 
> [1] https://github.com/apache/logging-log4j-jmx-gui
> 

Re: [VOTE] Release Apache Log4j JMX GUI 2.21.0 (RC2)

[Gary D. Gregory]

Probably not a blocker but the sha512 file can't be validated with the usual:

$ shasum --check apache-log4j-jmx-gui-2.21.0-src.zip.sha512

Instead I get:

shasum: /tmp/apache-log4j-jmx-gui-2.21.0-src.zip: No such file or directory
/tmp/apache-log4j-jmx-gui-2.21.0-src.zip: FAILED open or read
shasum: WARNING: 1 listed file could not be read

Because the sha512 file points to a non-existent folder "tmp" instead pointing 
directly to the file:

$ cat apache-log4j-jmx-gui-2.21.0-src.zip.sha512
5f1847021946f22a6a7e5b40ac9a409039bcb2fae668cf70439c814df4a5a6f770fef6b628c91e1dc317c7f684d5b1d13fdc112bd6369b16eff64e4ae1084474
  /tmp/apache-log4j-jmx-gui-2.21.0-src.zip

and eye-balling a sha512 is not "fun" ;-)

Gary

On 2023/09/15 08:54:45 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j JMX GUI 2.21.0 (RC2).
> 
> Source repository: https://github.com/apache/logging-log4j-jmx-gui
> Commit: c3056b340f57e2d6bd66b9f825722c336090d0d2
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-jmx-gui
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1175
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> 
> Please download, test, and cast your votes on this mailing list.
> 
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
> 
> This vote is open for 24 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> # RC1..RC2 changes
> 
> - Added `Main-Class` to `MANIFEST.MF`
> 
> # Release Notes
> 
> This marks the first release where the Log4j JMX GUI is released
> separately from the Log4j itself.
> 
> ## Changes
> 
> ### Added
> 
> * Project is moved to a new repository[1] with its own release cycle
> 
> [1] https://github.com/apache/logging-log4j-jmx-gui
> 

Spotless is annoying

[Gary D. Gregory]

How is this possible now that we use spotless in 2.x:

mvn clean install -pl log4j-api,log4j-core -DskipTests

[INFO] 
[INFO] Reactor Summary for Apache Log4j API 2.20.1-SNAPSHOT:
[INFO]
[INFO] Apache Log4j API ... FAILURE [ 22.303 s]
[INFO] Apache Log4j Core .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  25.370 s
[INFO] Finished at: 2023-09-01T08:10:43-04:00
[INFO] 
[ERROR] Failed to execute goal 
com.diffplug.spotless:spotless-maven-plugin:2.30.0:check (default-spotless) on 
project log4j-api: The following files had format violations:
[ERROR] src\main\java\org\apache\logging\log4j\internal\package-info.java
[ERROR] @@ -1,20 +1,20 @@
[ERROR] -/*\r\n
[ERROR] - * Licensed to the Apache Software Foundation (ASF) under one 
or more\r\n
[ERROR] - * contributor license agreements. See the NOTICE file 
distributed with\r\n
[ERROR] - * this work for additional information regarding copyright 
ownership.\r\n
[ERROR] - * The ASF licenses this file to You under the Apache license, 
Version 2.0\r\n
[ERROR] - * (the "License"); you may not use this file except in 
compliance with\r\n
[ERROR] - * the License. You may obtain a copy of the License at\r\n
[ERROR] - *\r\n
[ERROR] - *  http://www.apache.org/licenses/LICENSE-2.0\r\n
[ERROR] - *\r\n
[ERROR] - * Unless required by applicable law or agreed to in writing, 
software\r\n
[ERROR] - * distributed under the License is distributed on an "AS IS" 
BASIS,\r\n
[ERROR] - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either 
express or implied.\r\n
[ERROR] - * See the license for the specific language governing 
permissions and\r\n
[ERROR] - * limitations under the license.\r\n
[ERROR] - */\r\n
[ERROR] -/**\r\n
[ERROR] - * This package should be considered private.\r\n
[ERROR] - */\r\n
[ERROR] -package org.apache.logging.log4j.internal;\r\n
[ERROR] +/*\n
[ERROR] + * Licensed to the Apache Software Foundation (ASF) under one 
or more\n
[ERROR] + * contributor license agreements. See the NOTICE file 
distributed with\n
[ERROR] + * this work for additional information regarding copyright 
ownership.\n
[ERROR] + * The ASF licenses this file to You under the Apache license, 
Version 2.0\n
[ERROR] + * (the "License"); you may not use this file except in 
compliance with\n
[ERROR] + * the License. You may obtain a copy of the License at\n
[ERROR] + *\n
[ERROR] + *  http://www.apache.org/licenses/LICENSE-2.0\n
[ERROR] + *\n
[ERROR] + * Unless required by applicable law or agreed to in writing, 
software\n
[ERROR] + * distributed under the License is distributed on an "AS IS" 
BASIS,\n
[ERROR] + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either 
express or implied.\n
[ERROR] + * See the license for the specific language governing 
permissions and\n
[ERROR] + * limitations under the license.\n
[ERROR] + */\n
[ERROR] +/**\n
[ERROR] + * This package should be considered private.\n
[ERROR] + */\n
[ERROR] +package org.apache.logging.log4j.internal;\n
[ERROR] src\main\java\org\apache\logging\log4j\message\package-info.java
[ERROR] @@ -1,21 +1,21 @@
[ERROR] -/*\r\n
[ERROR] - * Licensed to the Apache Software Foundation (ASF) under one 
or more\r\n
[ERROR] - * contributor license agreements. See the NOTICE file 
distributed with\r\n
[ERROR] - * this work for additional information regarding copyright 
ownership.\r\n
[ERROR] - * The ASF licenses this file to You under the Apache license, 
Version 2.0\r\n
[ERROR] - * (the "License"); you may not use this file except in 
compliance with\r\n
[ERROR] ... (36 more lines that didn't fit)
[ERROR] Violations also present in:
[ERROR] src\main\java\org\apache\logging\log4j\package-info.java
[ERROR] src\main\java\org\apache\logging\log4j\simple\package-info.java
[ERROR] src\main\java\org\apache\logging\log4j\spi\package-info.java
[ERROR] src\main\java\org\apache\logging\log4j\status\package-info.java
[ERROR] src\main\java\org\apache\logging\log4j\util\package-info.java
[ERROR] Run 'mvn spotless:apply' to fix these violations.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors 

Re: [VOTE] Release Apache Log4j Transformation Tools 0.1.0

[Gary D. Gregory]

+1

Tests the src zip, asc and SHA file OK despite the SHA file being broken as 
Ralph noted (there should not be a target folder in the name).

mvn clean verify OK with:

Apache Maven 3.9.1 (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
Maven home: C:\java\apache-maven-3.9.1
Java version: 17.0.7, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.7.7-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Gary

On 2023/05/02 04:29:22 Ralph Goers wrote:
> +1
> 
> I checked out the tag and built the transformer and then ran it against one 
> of my projects at work and verified it generated some Log4j2Cache classes.
> 
> I verified the signature.
> I verified the checksum. While it is a good checksum the file name included 
> in the .sha512 file is target/apache-log4j-transform-0.1.0-src.zip which 
> causes "shasum -a 512 check” to fail. This should be fixed for the next 
> release.
> 
> Ralph
> 
> > On May 1, 2023, at 12:09 PM, Piotr P. Karwasz  
> > wrote:
> > 
> > The Apache Log4j Transformation Tools 0.1.0 release is now available for 
> > voting.
> > 
> > This is the first release and it contains two modules:
> > 
> > * [LOG4J2-3638]: Adds a bytecode transformation tool to provide
> > location information without reflection.
> > * [LOG4J2-673]: Adds a resource transformer for the Maven Shade Plugin
> > to merge `Log4j2Plugins.dat` plugin caches. Thanks to Eduard
> > Gizatullin.
> > 
> > Source repository: https://github.com/apache/logging-log4j-transform
> > Tag: rel/0.1.0-rc2
> > Commit: 7bb767c1466cd9faebfeeffa8136b231bf2b6fae
> > Artifacts: 
> > https://dist.apache.org/repos/dist/dev/logging/log4j-transform/0.1.0
> > Nexus repository:
> > https://repository.apache.org/content/repositories/orgapachelogging-1104
> > CI job run: 
> > https://github.com/apache/logging-log4j-transform/actions/runs/4853722893
> > Signing key: 
> > https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index
> > 
> > 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 All votes are welcome and we
> > encourage everyone to test the release, but only the Logging Services
> > PMC votes are officially counted. At least 3 +1 votes and more
> > positive than negative votes are required.
> > 
> > Countdown: 
> > https://www.timeanddate.com/countdown/launch?iso=20230504T2115=4162=cursive
> > 
> > Piotr
> 
> 

Re: [VOTE] Release Apache Log4j Transformation Tools 0.1.0

[Gary D. Gregory]

HI Ralph: Nitpicking: I'm pretty sure you're supposed to test the src zip, not 
the repo. In theory these two are different because the zip should not contain 
extra non-source junk like the .github folder.

Gary

On 2023/05/02 04:29:22 Ralph Goers wrote:
> +1
> 
> I checked out the tag and built the transformer and then ran it against one 
> of my projects at work and verified it generated some Log4j2Cache classes.
> 
> I verified the signature.
> I verified the checksum. While it is a good checksum the file name included 
> in the .sha512 file is target/apache-log4j-transform-0.1.0-src.zip which 
> causes "shasum -a 512 check” to fail. This should be fixed for the next 
> release.
> 
> Ralph
> 
> > On May 1, 2023, at 12:09 PM, Piotr P. Karwasz  
> > wrote:
> > 
> > The Apache Log4j Transformation Tools 0.1.0 release is now available for 
> > voting.
> > 
> > This is the first release and it contains two modules:
> > 
> > * [LOG4J2-3638]: Adds a bytecode transformation tool to provide
> > location information without reflection.
> > * [LOG4J2-673]: Adds a resource transformer for the Maven Shade Plugin
> > to merge `Log4j2Plugins.dat` plugin caches. Thanks to Eduard
> > Gizatullin.
> > 
> > Source repository: https://github.com/apache/logging-log4j-transform
> > Tag: rel/0.1.0-rc2
> > Commit: 7bb767c1466cd9faebfeeffa8136b231bf2b6fae
> > Artifacts: 
> > https://dist.apache.org/repos/dist/dev/logging/log4j-transform/0.1.0
> > Nexus repository:
> > https://repository.apache.org/content/repositories/orgapachelogging-1104
> > CI job run: 
> > https://github.com/apache/logging-log4j-transform/actions/runs/4853722893
> > Signing key: 
> > https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index
> > 
> > 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 All votes are welcome and we
> > encourage everyone to test the release, but only the Logging Services
> > PMC votes are officially counted. At least 3 +1 votes and more
> > positive than negative votes are required.
> > 
> > Countdown: 
> > https://www.timeanddate.com/countdown/launch?iso=20230504T2115=4162=cursive
> > 
> > Piotr
> 
> 

Re: [VOTE] Release Apache Log4j Transformation Tools 0.1.0

[Gary D. Gregory]

Another needed clean-up (not a blocker): The zip file has all sorts of git 
junk: a .github folder, a .gitignore file, and a .mvn folder (I certainly don't 
want extra maven junk either but that's just me)? There should only _sources_, 
not a snapshot of all files in the github repo. For example, see 
https://dlcdn.apache.org/logging/log4j/2.20.0/apache-log4j-2.20.0-bin.zip

Gary


On 2023/05/01 19:09:37 "Piotr P. Karwasz" wrote:
> The Apache Log4j Transformation Tools 0.1.0 release is now available for 
> voting.
> 
> This is the first release and it contains two modules:
> 
> * [LOG4J2-3638]: Adds a bytecode transformation tool to provide
> location information without reflection.
> * [LOG4J2-673]: Adds a resource transformer for the Maven Shade Plugin
> to merge `Log4j2Plugins.dat` plugin caches. Thanks to Eduard
> Gizatullin.
> 
> Source repository: https://github.com/apache/logging-log4j-transform
> Tag: rel/0.1.0-rc2
> Commit: 7bb767c1466cd9faebfeeffa8136b231bf2b6fae
> Artifacts: 
> https://dist.apache.org/repos/dist/dev/logging/log4j-transform/0.1.0
> Nexus repository:
> https://repository.apache.org/content/repositories/orgapachelogging-1104
> CI job run: 
> https://github.com/apache/logging-log4j-transform/actions/runs/4853722893
> Signing key: 
> https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index
> 
> 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 All votes are welcome and we
> encourage everyone to test the release, but only the Logging Services
> PMC votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> Countdown: 
> https://www.timeanddate.com/countdown/launch?iso=20230504T2115=4162=cursive
> 
> Piotr
> 

Re: [VOTE] Release Apache Log4j Transformation Tools 0.1.0

[Gary D. Gregory]

Note:

> Signing key: 
> https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index

A random link on the internet is irrelevant, what matters is what is in our 
KEYS file at:
https://downloads.apache.org/logging/KEYS

Gary

On 2023/05/01 19:09:37 "Piotr P. Karwasz" wrote:
> The Apache Log4j Transformation Tools 0.1.0 release is now available for 
> voting.
> 
> This is the first release and it contains two modules:
> 
> * [LOG4J2-3638]: Adds a bytecode transformation tool to provide
> location information without reflection.
> * [LOG4J2-673]: Adds a resource transformer for the Maven Shade Plugin
> to merge `Log4j2Plugins.dat` plugin caches. Thanks to Eduard
> Gizatullin.
> 
> Source repository: https://github.com/apache/logging-log4j-transform
> Tag: rel/0.1.0-rc2
> Commit: 7bb767c1466cd9faebfeeffa8136b231bf2b6fae
> Artifacts: 
> https://dist.apache.org/repos/dist/dev/logging/log4j-transform/0.1.0
> Nexus repository:
> https://repository.apache.org/content/repositories/orgapachelogging-1104
> CI job run: 
> https://github.com/apache/logging-log4j-transform/actions/runs/4853722893
> Signing key: 
> https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index
> 
> 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 All votes are welcome and we
> encourage everyone to test the release, but only the Logging Services
> PMC votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
> 
> Countdown: 
> https://www.timeanddate.com/countdown/launch?iso=20230504T2115=4162=cursive
> 
> Piotr
> 

Re: [VOTE] Release Apache Log4j Tools 0.3.0

[Gary D. Gregory]

Based on the src zip download:

(Please see my notes below for 1 improvement to the sha file)

mvn clean verify

Gives me:

[INFO] --- spotless:2.35.0:check (default-spotless) @ log4j-changelog ---
[INFO] Index file does not exist. Fallback to an empty index
[INFO] Spotless.Java is keeping 24 files clean - 24 needs changes to be clean, 
0 were already clean, 0 were skipped because caching determined they were 
already clean
[INFO] 
[INFO] Reactor Summary for log4j-tools-bom 0.3.0:
[INFO]
[INFO] log4j-tools-bom  SUCCESS [  3.313 s]
[INFO] log4j-tools-parent . SUCCESS [  8.199 s]
[INFO] log4j-changelog  FAILURE [ 13.450 s]
[INFO] log4j-changelog-maven-plugin ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  25.218 s
[INFO] Finished at: 2023-03-15T17:57:20-04:00
[INFO] 
[ERROR] Failed to execute goal 
com.diffplug.spotless:spotless-maven-plugin:2.35.0:check (default-spotless) on 
project log4j-changelog: The following files had format violations:
[ERROR] src\main\java\org\apache\logging\log4j\changelog\ChangelogEntry.java
[ERROR] @@ -1,206 +1,206 @@
[ERROR] -/*\n
[ERROR] - * Licensed to the Apache Software Foundation (ASF) under one 
or more\n
[ERROR] - * contributor license agreements. See the NOTICE file 
distributed with\n
[ERROR] - * this work for additional information regarding copyright 
ownership.\n
[ERROR] - * The ASF licenses this file to You under the Apache license, 
Version 2.0\n
[ERROR] - * (the "License"); you may not use this file except in 
compliance with\n
[ERROR] - * the License. You may obtain a copy of the License at\n
[ERROR] - *\n
[ERROR] - *  http://www.apache.org/licenses/LICENSE-2.0\n
[ERROR] - *\n
[ERROR] - * Unless required by applicable law or agreed to in writing, 
software\n
[ERROR] - * distributed under the License is distributed on an "AS IS" 
BASIS,\n
[ERROR] - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either 
express or implied.\n
[ERROR] - * See the license for the specific language governing 
permissions and\n
[ERROR] - * limitations under the license.\n
[ERROR] - */\n
[ERROR] -package org.apache.logging.log4j.changelog;\n
[ERROR] -\n
[ERROR] -import java.nio.file.Path;\n
[ERROR] -import java.util.List;\n
[ERROR] -import java.util.Locale;\n
[ERROR] -import java.util.stream.Collectors;\n
[ERROR] -\n
[ERROR] -import org.apache.logging.log4j.changelog.util.StringUtils;\n
[ERROR] -import org.apache.logging.log4j.changelog.util.XmlReader;\n
[ERROR] -import org.apache.logging.log4j.changelog.util.XmlWriter;\n
[ERROR] -\n
[ERROR] -import edu.umd.cs.findbugs.annotations.Nullable;\n
[ERROR] -import org.w3c.dom.Element;\n
[ERROR] -\n
[ERROR] -public final class ChangelogEntry {\n
[ERROR] -\n
[ERROR] -public final Type type;\n
[ERROR] -\n
[ERROR] -public final List issues;\n
[ERROR] -\n
[ERROR] -public final List authors;\n
[ERROR] -\n
[ERROR] -public final Description description;\n
[ERROR] -\n
[ERROR] -public enum Type {\n
[ERROR] -\n
[ERROR] -ADDED,\n
[ERROR] -\n
[ERROR] -CHANGED,\n
[ERROR] -\n
[ERROR] -DEPRECATED,\n
[ERROR] -\n
[ERROR] ... (364 more lines that didn't fit)
[ERROR] Violations also present in 23 other files.
[ERROR] Run 'mvn spotless:apply' to fix these violations.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :log4j-changelog

Using:

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: C:\java\apache-maven-3.9.0
Java version: 17.0.6, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.6.10-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

FYI:

$ cat apache-log4j-tools-0.3.0-src.zip.sha512

Re: [VOTE] Release Apache Log4j Tools 0.3.0

[Gary D. Gregory]

On 2023/03/15 21:46:10 "Gary D. Gregory" wrote:
> IMO, VOTE emails should contain a link to the appropriate KEYS file.

FTR: https://downloads.apache.org/logging/KEYS

Gary

> 
> Gary
> 
> On 2023/03/14 21:08:39 Volkan Yazıcı wrote:
> > The Apache Log4j Tools 0.3.0 release is now available for voting.
> > 
> > This release contains the following minor enhancements:
> > 
> > * Upgrade the compiler version to Java 17, yet still target Java 8
> > * Support multiple and formatting-agnostic template files (#44)
> > * The changelog release models passed to the index template file
> > (`.index.adoc.ftl`) is enriched with `changelogEntryCount` fields
> > (#37)
> > 
> > Source repository: https://github.com/apache/logging-log4j-tools
> > Tag: rel/0.3.0-rc.1
> > Commit: 243017d3f60410780dd6d15b8b677bc5b018d1cf
> > CI run: 
> > https://github.com/apache/logging-log4j-tools/actions/runs/4420103110
> > Artifacts: https://dist.apache.org/repos/dist/dev/logging/log4j/
> > Nexus repository:
> > https://repository.apache.org/content/repositories/orgapachelogging-1100
> > Signing key: 
> > https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index
> > 
> > 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 the Logging Services PMC votes are officially counted. At least 3
> > +1 votes and more positive than negative votes are required.
> > 
> 

Re: [VOTE] Release Apache Log4j Tools 0.3.0

[Gary D. Gregory]

IMO, VOTE emails should contain a link to the appropriate KEYS file.

Gary

On 2023/03/14 21:08:39 Volkan Yazıcı wrote:
> The Apache Log4j Tools 0.3.0 release is now available for voting.
> 
> This release contains the following minor enhancements:
> 
> * Upgrade the compiler version to Java 17, yet still target Java 8
> * Support multiple and formatting-agnostic template files (#44)
> * The changelog release models passed to the index template file
> (`.index.adoc.ftl`) is enriched with `changelogEntryCount` fields
> (#37)
> 
> Source repository: https://github.com/apache/logging-log4j-tools
> Tag: rel/0.3.0-rc.1
> Commit: 243017d3f60410780dd6d15b8b677bc5b018d1cf
> CI run: https://github.com/apache/logging-log4j-tools/actions/runs/4420103110
> Artifacts: https://dist.apache.org/repos/dist/dev/logging/log4j/
> Nexus repository:
> https://repository.apache.org/content/repositories/orgapachelogging-1100
> Signing key: 
> https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index
> 
> 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 the Logging Services PMC votes are officially counted. At least 3
> +1 votes and more positive than negative votes are required.
> 

Re: [VOTE] Release Apache Log4j Tools 0.3.0

[Gary D. Gregory]

There are still 0.2.0 files in /dev/logging/log4j ! Delete please.

Gary

On 2023/03/14 21:08:39 Volkan Yazıcı wrote:
> The Apache Log4j Tools 0.3.0 release is now available for voting.
> 
> This release contains the following minor enhancements:
> 
> * Upgrade the compiler version to Java 17, yet still target Java 8
> * Support multiple and formatting-agnostic template files (#44)
> * The changelog release models passed to the index template file
> (`.index.adoc.ftl`) is enriched with `changelogEntryCount` fields
> (#37)
> 
> Source repository: https://github.com/apache/logging-log4j-tools
> Tag: rel/0.3.0-rc.1
> Commit: 243017d3f60410780dd6d15b8b677bc5b018d1cf
> CI run: https://github.com/apache/logging-log4j-tools/actions/runs/4420103110
> Artifacts: https://dist.apache.org/repos/dist/dev/logging/log4j/
> Nexus repository:
> https://repository.apache.org/content/repositories/orgapachelogging-1100
> Signing key: 
> https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index
> 
> 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 the Logging Services PMC votes are officially counted. At least 3
> +1 votes and more positive than negative votes are required.
> 

Re: [VOTE] Release Apache Log4j Tools 0.3.0

[Gary D. Gregory]

Arg, I downloaded the wrong files.

Ralph and all RMs: Please delete files post release from /dev/logging/log4j

Gary

On 2023/03/14 21:08:39 Volkan Yazıcı wrote:
> The Apache Log4j Tools 0.3.0 release is now available for voting.
> 
> This release contains the following minor enhancements:
> 
> * Upgrade the compiler version to Java 17, yet still target Java 8
> * Support multiple and formatting-agnostic template files (#44)
> * The changelog release models passed to the index template file
> (`.index.adoc.ftl`) is enriched with `changelogEntryCount` fields
> (#37)
> 
> Source repository: https://github.com/apache/logging-log4j-tools
> Tag: rel/0.3.0-rc.1
> Commit: 243017d3f60410780dd6d15b8b677bc5b018d1cf
> CI run: https://github.com/apache/logging-log4j-tools/actions/runs/4420103110
> Artifacts: https://dist.apache.org/repos/dist/dev/logging/log4j/
> Nexus repository:
> https://repository.apache.org/content/repositories/orgapachelogging-1100
> Signing key: 
> https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index
> 
> 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 the Logging Services PMC votes are officially counted. At least 3
> +1 votes and more positive than negative votes are required.
> 

Re: [VOTE] Release Apache Log4j Tools 0.3.0

[Gary D. Gregory]

Hi All,

I do not think we should clutter things up by publishing two sets of SHA files 
(256 & 512), SHA-512 only is plenty IMO.

Gary

On 2023/03/14 21:08:39 Volkan Yazıcı wrote:
> The Apache Log4j Tools 0.3.0 release is now available for voting.
> 
> This release contains the following minor enhancements:
> 
> * Upgrade the compiler version to Java 17, yet still target Java 8
> * Support multiple and formatting-agnostic template files (#44)
> * The changelog release models passed to the index template file
> (`.index.adoc.ftl`) is enriched with `changelogEntryCount` fields
> (#37)
> 
> Source repository: https://github.com/apache/logging-log4j-tools
> Tag: rel/0.3.0-rc.1
> Commit: 243017d3f60410780dd6d15b8b677bc5b018d1cf
> CI run: https://github.com/apache/logging-log4j-tools/actions/runs/4420103110
> Artifacts: https://dist.apache.org/repos/dist/dev/logging/log4j/
> Nexus repository:
> https://repository.apache.org/content/repositories/orgapachelogging-1100
> Signing key: 
> https://keyserver.ubuntu.com/pks/lookup?search=077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0=on=index
> 
> 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 the Logging Services PMC votes are officially counted. At least 3
> +1 votes and more positive than negative votes are required.
> 

Re: [log4j] Checkout from git is broken

[Gary D. Gregory]

On 2023/03/10 12:42:00 Volkan Yazıcı wrote:
> If you browse to https://github.com/apache/logging-log4j2 and clone the
> repository as described there:
> 
> git clone g...@github.com:apache/logging-log4j2.git
> 
> This not only works, but also lands you on the right branch: `2.x`.

Pardon me for being dense but I've lost my patience, I'm trying to do many 
things today and getting nowhere with Log4j:

```
C:\tmp>git clone g...@github.com:apache/logging-log4j2.git foo
Cloning into 'foo'...
The authenticity of host 'github.com (140.82.112.4)' can't be established.
ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'github.com' (ED25519) to the list of known hosts.
g...@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
```

Did you mean for "g...@github.com" to stand in for something else?

"> If you browse to https://github.com/apache/logging-log4j2 and clone the
> repository as described there:"

As described there? The word "clone" does not even appear on that page. What am 
I missing?

The GH UI in the "Code" drop-down says: 
https://github.com/apache/logging-log4j2.git

So frustrated,
Gary

> 
> On Fri, Mar 10, 2023 at 12:47 PM Gary Gregory 
> wrote:
> 
> > So the branch renaming broke cloning and checking out code with the most
> > basic git command? At least that's what the side effect seems to me. What's
> > the fix? Or will no one ever be able to say 'git clone' as below and have
> > it just work?
> >
> > Gary
> >
> > On Fri, Mar 10, 2023, 05:18 Volkan Yazıcı  wrote:
> >
> > > We mention the `gitbox` keyword neither in the sources, nor in the docs.
> > >
> > > There is a GitHub link at the top right corner of every page in the
> > > website.
> > >
> > > `pom.xml`s SCM block points to GitHub.
> > >
> > > `CONTRIBUTING.md` only hints to GitHub resources – though I agree there
> > is
> > > no direct link to the repository there.
> > >
> > > I think everybody _assumes_ GitHub is the default repository. Maybe we
> > > should clearly document this.
> > >
> > > Regarding the `nonexistent ref` error you get, we have renamed quite some
> > > branches[1]. In particular, `master` → `main` and `release-2.x` → `2.x`.
> > >
> > > I hope this clarifies things for you.
> > >
> > > [1] https://lists.apache.org/thread/41wds37l4xmfzljgsgvplny811wd1v37
> > >
> > > On Thu, Mar 9, 2023 at 11:51 PM Gary D. Gregory 
> > > wrote:
> > >
> > > > Hi All:
> > > >
> > > > My expectation is that:
> > > >
> > > > C:\Users\ggregory\git\a>git clone
> > > > https://gitbox.apache.org/repos/asf/logging-log4j2.git logging-log4j3
> > > >
> > > > Would clone and checkout master (or main or whatever the default branch
> > > is
> > > > called now) but instead, I get an empty folder and this output:
> > > >
> > > > Cloning into 'logging-log4j3'...
> > > > remote: Enumerating objects: 262413, done.
> > > > remote: Counting objects: 100% (262413/262413), done.
> > > > remote: Compressing objects: 100% (68647/68647), done.
> > > > remote: Total 262413 (delta 127358), reused 256238 (delta 122788)
> > > > Receiving objects: 100% (262413/262413), 38.27 MiB | 11.31 MiB/s, done.
> > > > Resolving deltas: 100% (127358/127358), done.
> > > > warning: remote HEAD refers to nonexistent ref, unable to checkout
> > > >
> > > > This says nothing to help:
> > > > https://github.com/apache/logging-log4j2/blob/2.x/BUILDING.md
> > > > and nothing jumps out at me on the main page
> > > > https://logging.apache.org/log4j/2.x/index.html
> > > >
> > > > So... what's the magic missing?
> > > >
> > > > TY!
> > > > Gary
> > > >
> > > >
> > >
> >
> 

[log4j] 2.x changelog

[Gary D. Gregory]

Hi All:

Where are the steps I can follow to add an entry to the changelog (in this case 
for 2.20.1)?

TY!
Gary

Re: Compiling with JDK 11 or JDK 17

[Gary D. Gregory]

I'm OK with our tooling requiring whatever makes our lives simplest as long we 
can guarantee that the target byte codes and *API calls* will work on Java 8 
for 2.x. 

Gary

On 2023/03/08 19:29:29 Volkan Yazıcı wrote:
> I completely support both initiatives:
> 
> 1. Moving the JDK to 17 (why stay at 11?)
> 2. Moving `log4j-jmx-gui` to a separate repository
> 
> We have pulled a similar stunt in `log4j-tools`: it uses JDK 11, though
> targets 8. We can easily move `log4j-jmx-gui` to a separate repository by
> copying the project infra (README, CI, release process, etc.) from
> `log4j-tools`.
> 
> On Fri, Mar 3, 2023 at 10:45 PM Piotr P. Karwasz 
> wrote:
> 
> > Hi,
> >
> > Compiling 2.x using JDK 8 requires a lot of tricks:
> >
> > * Surefire scans classes using the main Maven JDK, so we must be sure
> > `module-info.class` and other Java 9+ classes are not on the test
> > classpath. This basically means we need to delete them before testing
> > and creating them afterwards.
> > * We need toolchains even if we disable tests,
> > * Some Maven or compiler plugins (like Error Prone) either require
> > Java 11 or are hard to configure on Java 8.
> >
> > That is why I would propose to bump the JDK requirement in the POM
> > file to JDK 11+ (for `log4j-jpl`) and add `--release 8` everywhere it
> > makes sense.
> >
> > For reproducibility purposes the CI and apache-release profiles would
> > still need to fix a JDK (JDK 17?) for compilation and a JRE (JRE 8)
> > for testing. But a casual user will be able to run the build process
> > without toolchains.
> >
> > I have a working prototype on this branch:
> >
> > https://github.com/ppkarwasz/logging-log4j2/tree/java17
> >
> > The only problem I wasn't able to solve is to compile `log4j-jmx-gui`
> > with JDK 11+: it requires `jconsole.jar` in the classpath, all JDK's
> > after 8 have a module for that. I think we could move it to a separate
> > repo.
> >
> > Remark that `log4j-api`, which uses `sun.reflect.Reflection`, compiles
> > perfectly with JDK 17 and `--release 8`.
> >
> > Piotr
> >
> 

[log4j] Checkout from git is broken

[Gary D. Gregory]

Hi All:

My expectation is that:

C:\Users\ggregory\git\a>git clone 
https://gitbox.apache.org/repos/asf/logging-log4j2.git logging-log4j3

Would clone and checkout master (or main or whatever the default branch is 
called now) but instead, I get an empty folder and this output:

Cloning into 'logging-log4j3'...
remote: Enumerating objects: 262413, done.
remote: Counting objects: 100% (262413/262413), done.
remote: Compressing objects: 100% (68647/68647), done.
remote: Total 262413 (delta 127358), reused 256238 (delta 122788)
Receiving objects: 100% (262413/262413), 38.27 MiB | 11.31 MiB/s, done.
Resolving deltas: 100% (127358/127358), done.
warning: remote HEAD refers to nonexistent ref, unable to checkout

This says nothing to help: 
https://github.com/apache/logging-log4j2/blob/2.x/BUILDING.md
and nothing jumps out at me on the main page 
https://logging.apache.org/log4j/2.x/index.html

So... what's the magic missing?

TY!
Gary

Re: Broken build

[Gary D. Gregory]

On Windows, I get:

[INFO] Running org.apache.logging.log4j.status.StatusConsoleListenerTest
[ERROR] Tests run: 41, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in org.apache.logging.log4j.spi.MutableThreadContextStackTest
[ERROR] org.apache.logging.log4j.LoggerTest.flowTracingMessage  Time elapsed: 
0.48 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <2> but was: <3>
at 
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at 
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at 
org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at 
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at 
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:528)
at 
org.apache.logging.log4j.LoggerTest.flowTracingMessage(LoggerTest.java:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
at 
org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
at 
org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
at 
org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
at 
org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:138)
at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
at 
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
at 
org.junit.platform.engine.support.hierarchical.ForkJoinPoolHierarchicalTestExecutorService$ExclusiveTask.compute(ForkJoinPoolHierarchicalTestExecutorService.java:185)
at java.util.concurrent.RecursiveAction.exec(RecursiveAction.java:189)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinTask.doJoin(ForkJoinTask.java:389)
at 

Re: [VOTE] Release Apache Log4j 2.19.0-rc2

[Gary D. Gregory]

+1

Building 'mvn -V clean install' from src zip with:

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: C:\Java\apache-maven-3.8.6
Java version: 1.8.0_342, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.342.7-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

ASC file OK, SHA512 OK.

Gary

On 2022/09/15 13:55:06 "Gary D. Gregory" wrote:
> Darn, that looks like a random error, my current build attempt made it past 
> that module.
> 
> Gary
> 
> On 2022/09/14 20:30:04 "Gary D. Gregory" wrote:
> > Building from the src zip on Windows 10 with 'mvn -V clean install', I get 
> > this failure:
> > 
> > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> > Maven home: C:\Java\apache-maven-3.8.6
> > Java version: 1.8.0_342, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> > Adoptium\jdk-8.0.342.7-hotspot\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> > ...
> > [INFO] Running org.apache.logging.log4j.NoopThreadContextTest
> > [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> > 2.984 s <<< FAILURE! - in 
> > org.apache.logging.log4j.message.StructuredDataMessageTest
> > [ERROR] org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2  
> > Time elapsed: 0.011 s  <<< FAILURE!
> > org.opentest4j.AssertionFailedError: expected: <2> but was: <1>
> > at 
> > org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> > at 
> > org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> > at 
> > org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> > at 
> > org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> > at 
> > org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> > at 
> > org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
> > at 
> > org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2(LoggerTest.java:125)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at 
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > at 
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:498)
> > at 
> > org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
> > at 
> > org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> > at 
> > org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> > at 
> > org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
> > at 
> > org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
> > at 
> > org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
> > at 
> > org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
> > at 
> > org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
> > at 
> > org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
> > at 
> > org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
> > at 
> > org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
> > at 
> > org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
> > at 
> > org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
> > at 
> > org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
> > at 
> > org.junit.jupiter.engine.descriptor.Tes

Re: [VOTE] Release Apache Log4j 2.19.0-rc2

[Gary D. Gregory]

On 2022/09/15 14:49:08 Matt Sicker wrote:
> That sounds like a flaky test. Sometimes those are actually caused by real 
> bugs, so feel free to file a Jira issue to follow up on it.

Here is a new ticket: https://issues.apache.org/jira/browse/LOG4J2-3599

Gary

> —
> Matt Sicker
> 
> > On Sep 15, 2022, at 08:55, Gary D. Gregory  wrote:
> > 
> > Darn, that looks like a random error, my current build attempt made it past 
> > that module.
> > 
> > Gary
> > 
> > On 2022/09/14 20:30:04 "Gary D. Gregory" wrote:
> >> Building from the src zip on Windows 10 with 'mvn -V clean install', I get 
> >> this failure:
> >> 
> >> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> >> Maven home: C:\Java\apache-maven-3.8.6
> >> Java version: 1.8.0_342, vendor: Temurin, runtime: C:\Program 
> >> Files\Eclipse Adoptium\jdk-8.0.342.7-hotspot\jre
> >> Default locale: en_US, platform encoding: Cp1252
> >> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> >> ...
> >> [INFO] Running org.apache.logging.log4j.NoopThreadContextTest
> >> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> >> 2.984 s <<< FAILURE! - in 
> >> org.apache.logging.log4j.message.StructuredDataMessageTest
> >> [ERROR] org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2 
> >>  Time elapsed: 0.011 s  <<< FAILURE!
> >> org.opentest4j.AssertionFailedError: expected: <2> but was: <1>
> >>at 
> >> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> >>at 
> >> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> >>at 
> >> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> >>at 
> >> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> >>at 
> >> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> >>at 
> >> org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
> >>at 
> >> org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2(LoggerTest.java:125)
> >>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>at 
> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >>at 
> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>at java.lang.reflect.Method.invoke(Method.java:498)
> >>at 
> >> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
> >>at 
> >> org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> >>at 
> >> org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> >>at 
> >> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
> >>at 
> >> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
> >>at 
> >> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
> >>at 
> >> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
> >>at 
> >> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
> >>at 
> >> org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
> >>at 
> >> org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
> >>at 
> >> org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
> >>at 
> >> org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
> >>at 
> >> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
> >>at 
> >> org.junit.jupiter.engine.execu

Re: [VOTE] Release Apache Log4j 2.19.0-rc2

[Gary D. Gregory]

Darn, that looks like a random error, my current build attempt made it past 
that module.

Gary

On 2022/09/14 20:30:04 "Gary D. Gregory" wrote:
> Building from the src zip on Windows 10 with 'mvn -V clean install', I get 
> this failure:
> 
> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> Maven home: C:\Java\apache-maven-3.8.6
> Java version: 1.8.0_342, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.342.7-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> ...
> [INFO] Running org.apache.logging.log4j.NoopThreadContextTest
> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.984 
> s <<< FAILURE! - in org.apache.logging.log4j.message.StructuredDataMessageTest
> [ERROR] org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2  
> Time elapsed: 0.011 s  <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: <2> but was: <1>
> at 
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at 
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at 
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at 
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> at 
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
> at 
> org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2(LoggerTest.java:125)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
> at 
> org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> at 
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> at 
> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
> at 
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
> at 
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
> at 
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
> at 
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
> at 
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
> at 
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
> at 
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
> at 
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
> at 
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
> at 
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
> at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:138)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
> at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit

Re: [VOTE] Release Apache Log4j 2.19.0-rc2

[Gary D. Gregory]

Building from the src zip on Windows 10 with 'mvn -V clean install', I get this 
failure:

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: C:\Java\apache-maven-3.8.6
Java version: 1.8.0_342, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.342.7-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
...
[INFO] Running org.apache.logging.log4j.NoopThreadContextTest
[ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.984 s 
<<< FAILURE! - in org.apache.logging.log4j.message.StructuredDataMessageTest
[ERROR] org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2  
Time elapsed: 0.011 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <2> but was: <1>
at 
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at 
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at 
org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at 
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at 
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
at 
org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2(LoggerTest.java:125)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
at 
org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
at 
org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
at 
org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
at 
org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:138)
at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
at 
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
at 

[jira] [Closed] (LOG4J2-91) NoSuchMethodError: org.apache.log4j.Category.log(Ljava/lang/String;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V

[Gary D. Gregory (JIRA)]

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

Gary D. Gregory closed LOG4J2-91.
-


Works like a charm :)

 NoSuchMethodError: 
 org.apache.log4j.Category.log(Ljava/lang/String;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V
 ---

 Key: LOG4J2-91
 URL: https://issues.apache.org/jira/browse/LOG4J2-91
 Project: Log4j 2
  Issue Type: Bug
  Components: log4j 1.2 emulation
Affects Versions: 2.0-beta1
 Environment: java version 1.7.0_07
 Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
 Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
Reporter: Gary D. Gregory
Assignee: Ralph Goers
 Fix For: 2.0-beta2


 I have an app that uses HtmlUnit which depends on Log4J 1.2.
 When I run it, I get:
 {noformat}
 Exception in thread main java.lang.NoSuchMethodError: 
 org.apache.log4j.Category.log(Ljava/lang/String;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V
   at 
 org.apache.commons.logging.impl.Log4JLogger.debug(Log4JLogger.java:177)
   at 
 com.gargoylesoftware.htmlunit.javascript.configuration.JavaScriptConfiguration.parseClassElement(JavaScriptConfiguration.java:394)
   at 
 com.gargoylesoftware.htmlunit.javascript.configuration.JavaScriptConfiguration.buildUsageMap(JavaScriptConfiguration.java:312)
   at 
 com.gargoylesoftware.htmlunit.javascript.configuration.JavaScriptConfiguration.init(JavaScriptConfiguration.java:147)
   at 
 com.gargoylesoftware.htmlunit.javascript.configuration.JavaScriptConfiguration.getInstance(JavaScriptConfiguration.java:237)
   at 
 com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine.init(JavaScriptEngine.java:116)
   at com.gargoylesoftware.htmlunit.WebClient.init(WebClient.java:219)
   at com.gargoylesoftware.htmlunit.WebClient.init(WebClient.java:193)
   at com.gargoylesoftware.htmlunit.WebClient.init(WebClient.java:184)
   at 
 com.c2g2.collect.BizJournalsPageCollector.init(BizJournalsPageCollector.java:50)
   at com.c2g2.site.SitesDb.newBizJournalsSiteDb(SitesDb.java:95)
   at com.c2g2.site.SitesDb.getSiteDbList(SitesDb.java:39)
   at com.c2g2.site.SitesDbCollector.run(SitesDbCollector.java:32)
   at com.c2g2.site.SitesDbCollector.main(SitesDbCollector.java:24)
 {noformat}
 My CP in Eclipse:
 {code:xml}
 ?xml version=1.0 encoding=UTF-8?
 classpath
   classpathentry kind=src path=src/main/java/
   classpathentry kind=con 
 path=org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/Oracle
  JRE 7 +NiN/
   classpathentry kind=lib path=lib/jetty-all-8.1.7.v20120910.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/commons-codec-1.6.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/commons-collections-3.2.1.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/commons-io-2.2.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/commons-lang3-3.1.jar 
 sourcepath=src/lib/commons-lang3-3.1-sources.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/commons-logging-1.1.1.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/cssparser-0.9.7.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/htmlunit-2.10.jar 
 sourcepath=src/lib/htmlunit-2.10-src.zip/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/htmlunit-core-js-2.10.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/httpclient-4.2.1.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/httpcore-4.2.1.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/httpmime-4.2.1.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/nekohtml-1.9.16.jar/
   classpathentry kind=lib path=lib/htmlunit-2.10/lib/sac-1.3.jar/
   classpathentry kind=lib 
 path=lib/htmlunit-2.10/lib/serializer-2.7.1.jar/
   classpathentry kind=lib path=lib/commons-vfs2-2.0.jar 
 sourcepath=src/lib/commons-vfs2-2.0-sources.jar/
   classpathentry kind=lib path=lib/joda-time-2.1.jar 
 sourcepath=src/lib/joda-time-2.1-sources.jar/
   classpathentry kind=lib path=lib/commons-csv-1.0-SNAPSHOT.jar 
 sourcepath=/commons-csv/src/
   classpathentry kind=lib path=lib/commons-email-1.2.jar 
 sourcepath=src/lib/commons-email-1.2-sources.jar/
   classpathentry kind=lib path=lib/mail-1.4.5.jar/
   classpathentry kind=lib path=lib/log4j-api-2.0-beta1.jar 
 sourcepath=src/lib/log4j-api-2.0-beta1-sources.jar/
   classpathentry kind=lib path=lib/log4j-core-2.0-beta1.jar 
 sourcepath=src/lib/log4j-core-2.0-beta1-sources.jar/
   classpathentry kind=lib path=lib/log4j12-api

[jira] [Created] (LOG4J2-91) NoSuchMethodError: org.apache.log4j.Category.log(Ljava/lang/String;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V

[Gary D. Gregory (JIRA)]

Gary D. Gregory created LOG4J2-91:
-

 Summary: NoSuchMethodError: 
org.apache.log4j.Category.log(Ljava/lang/String;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V
 Key: LOG4J2-91
 URL: https://issues.apache.org/jira/browse/LOG4J2-91
 Project: Log4j 2
  Issue Type: Bug
  Components: log4j 1.2 emulation
Affects Versions: 2.0-beta1
 Environment: java version 1.7.0_07
Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)

Reporter: Gary D. Gregory


I have an app that uses HtmlUnit which depends on Log4J 1.2.

When I run it, I get:

{noformat}
Exception in thread main java.lang.NoSuchMethodError: 
org.apache.log4j.Category.log(Ljava/lang/String;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V
at 
org.apache.commons.logging.impl.Log4JLogger.debug(Log4JLogger.java:177)
at 
com.gargoylesoftware.htmlunit.javascript.configuration.JavaScriptConfiguration.parseClassElement(JavaScriptConfiguration.java:394)
at 
com.gargoylesoftware.htmlunit.javascript.configuration.JavaScriptConfiguration.buildUsageMap(JavaScriptConfiguration.java:312)
at 
com.gargoylesoftware.htmlunit.javascript.configuration.JavaScriptConfiguration.init(JavaScriptConfiguration.java:147)
at 
com.gargoylesoftware.htmlunit.javascript.configuration.JavaScriptConfiguration.getInstance(JavaScriptConfiguration.java:237)
at 
com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine.init(JavaScriptEngine.java:116)
at com.gargoylesoftware.htmlunit.WebClient.init(WebClient.java:219)
at com.gargoylesoftware.htmlunit.WebClient.init(WebClient.java:193)
at com.gargoylesoftware.htmlunit.WebClient.init(WebClient.java:184)
at 
com.c2g2.collect.BizJournalsPageCollector.init(BizJournalsPageCollector.java:50)
at com.c2g2.site.SitesDb.newBizJournalsSiteDb(SitesDb.java:95)
at com.c2g2.site.SitesDb.getSiteDbList(SitesDb.java:39)
at com.c2g2.site.SitesDbCollector.run(SitesDbCollector.java:32)
at com.c2g2.site.SitesDbCollector.main(SitesDbCollector.java:24)
{noformat}

My CP in Eclipse:

{code:xml}
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=src/main/java/
classpathentry kind=con 
path=org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/Oracle
 JRE 7 +NiN/
classpathentry kind=lib path=lib/jetty-all-8.1.7.v20120910.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/commons-codec-1.6.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/commons-collections-3.2.1.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/commons-io-2.2.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/commons-lang3-3.1.jar 
sourcepath=src/lib/commons-lang3-3.1-sources.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/commons-logging-1.1.1.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/cssparser-0.9.7.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/htmlunit-2.10.jar 
sourcepath=src/lib/htmlunit-2.10-src.zip/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/htmlunit-core-js-2.10.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/httpclient-4.2.1.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/httpcore-4.2.1.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/httpmime-4.2.1.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/nekohtml-1.9.16.jar/
classpathentry kind=lib path=lib/htmlunit-2.10/lib/sac-1.3.jar/
classpathentry kind=lib 
path=lib/htmlunit-2.10/lib/serializer-2.7.1.jar/
classpathentry kind=lib path=lib/commons-vfs2-2.0.jar 
sourcepath=src/lib/commons-vfs2-2.0-sources.jar/
classpathentry kind=lib path=lib/joda-time-2.1.jar 
sourcepath=src/lib/joda-time-2.1-sources.jar/
classpathentry kind=lib path=lib/commons-csv-1.0-SNAPSHOT.jar 
sourcepath=/commons-csv/src/
classpathentry kind=lib path=lib/commons-email-1.2.jar 
sourcepath=src/lib/commons-email-1.2-sources.jar/
classpathentry kind=lib path=lib/mail-1.4.5.jar/
classpathentry kind=lib path=lib/log4j-api-2.0-beta1.jar 
sourcepath=src/lib/log4j-api-2.0-beta1-sources.jar/
classpathentry kind=lib path=lib/log4j-core-2.0-beta1.jar 
sourcepath=src/lib/log4j-core-2.0-beta1-sources.jar/
classpathentry kind=lib path=lib/log4j12-api-2.0-beta1.jar/
classpathentry kind=output path=bin/
/classpath
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LOG4J2-30) Author tags

[Gary D. Gregory (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13264300#comment-13264300
 ] 

Gary D. Gregory commented on LOG4J2-30:
---

+1 to remove author tags.

 Author tags
 ---

 Key: LOG4J2-30
 URL: https://issues.apache.org/jira/browse/LOG4J2-30
 Project: Log4j 2
  Issue Type: Wish
Reporter: Curt Arnold
Priority: Minor

 Logging this as a bug so that it eventually gets resolved.
 From log4j-dev thread Future development of log4j 2.0
 On 20/02/2010 12:42 AM, Christian Grobmeier wrote:
 there might be other discussions which could
 lead to frustrations on several sides. I think on discussions like
 having author tags and such.
 On Feb 19, 2010, at 5:57 PM, Ceki Gülcü wrote:
 Author tags is a way of recognizing contributors. Recognition is a
 very important aspect of oss.
 ---
 Author tags have been discouraged by the board, 
 http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt
  (section D)
 This statement by Dirk-Wlllem van Gulik, then president of the ASF, expands 
 on the rationale: 
 http://marc.info/?l=xml-cocoon-devm=107787986409413w=2
 Don't think we need to tackle the issue until there is code someone wants to 
 tag.  I'm not planning on tagging any code that I initially develop.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Created] (LOG4J2-55) Configure from an InputStream

[Gary D. Gregory (Created) (JIRA)]

Configure from an InputStream
-

 Key: LOG4J2-55
 URL: https://issues.apache.org/jira/browse/LOG4J2-55
 Project: Log4j 2
  Issue Type: Improvement
  Components: Configurators
 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
Maven home: C:\Java\apache-maven-3.0.3\bin\..
Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_29\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Gary D. Gregory


This issue is the version 2 side of 
https://issues.apache.org/bugzilla/show_bug.cgi?id=52094

Add the ability to Configure from an InputStream, not just a URL.

The goal is to be able to configure from an Apache Commons VFS FileObject. The
only way to get the contents of a FileObject is to say
getContents().getInputStream()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org