Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create "Migrate from Log4j 2" page #2654

Merged
merged 1 commit into from
Jun 13, 2024
Merged

Create "Migrate from Log4j 2" page #2654

merged 1 commit into from
Jun 13, 2024

Conversation

ppkarwasz
Copy link
Contributor

We create a "Migrate from Log4j 2" that specifies:

  • the required changes in the runtime classpath due to the splitting of modules,
  • a warning about the change of the naming convention for configuration properties,
  • a list of migration rules for users that love the Java properties configuration format.

Part of #2540.

We create a "Migrate from Log4j 2" that specifies:

- the required changes in the runtime classpath due to the splitting of
  modules,
- a warning about the change of the naming convention for configuration
  properties,
- a list of migration rules for users that love the Java properties
  configuration format.

Part of #2540.
@ppkarwasz ppkarwasz force-pushed the doc/main/migration branch from c9bc2d4 to 7b53c64 Compare June 13, 2024 20:52
@ppkarwasz ppkarwasz merged commit 7b53c64 into main Jun 13, 2024
5 of 6 checks passed
@ppkarwasz ppkarwasz deleted the doc/main/migration branch June 13, 2024 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants