Migrate JUL to Log4j 2.x API
org.openrewrite.java.logging.log4j.JulToLog4j
Transforms code written using java.util.logging
to use Log4j 2.x API.
Tags
- java-util-logging
- logging
- log4j
Recipe source
GitHub, Issue Tracker, Maven Central
This recipe is composed of more than one recipe. If you want to customize the set of recipes this is composed of, you can find and copy the GitHub source for the recipe from the link above.
Definition
- Recipe List
- Yaml Recipe List
- Replace JUL Level arguments with the corresponding method calls
- Change method target to static
- methodPattern:
java.util.logging.Logger getLogger(..)
- fullyQualifiedTargetTypeName:
org.apache.logging.log4j.LogManager
- methodPattern:
- Change method name
- methodPattern:
java.util.logging.Logger config(..)
- newMethodName:
info
- methodPattern:
- Change method name
- methodPattern:
java.util.logging.Logger fine(..)
- newMethodName:
debug
- methodPattern:
- Change method name
- methodPattern:
java.util.logging.Logger finer(..)
- newMethodName:
trace
- methodPattern:
- Change method name
- methodPattern:
java.util.logging.Logger finest(..)
- newMethodName:
trace
- methodPattern:
- Change method name
- methodPattern:
java.util.logging.Logger severe(..)
- newMethodName:
error
- methodPattern:
- Change method name
- methodPattern:
java.util.logging.Logger warning(..)
- newMethodName:
warn
- methodPattern:
- Rewrites JUL's Logger#entering method to Log4j API
- Rewrites JUL's Logger#exiting method to Log4j API
- Change type
- oldFullyQualifiedTypeName:
java.util.logging.Logger
- newFullyQualifiedTypeName:
org.apache.logging.log4j.Logger
- oldFullyQualifiedTypeName:
- Replace any Lombok log annotations with target logging framework annotation
- loggingFramework:
Log4j2
- loggingFramework:
---
type: specs.openrewrite.org/v1beta/recipe
name: org.openrewrite.java.logging.log4j.JulToLog4j
displayName: Migrate JUL to Log4j 2.x API
description: Transforms code written using `java.util.logging` to use Log4j 2.x API.
tags:
- java-util-logging
- logging
- log4j
recipeList:
- org.openrewrite.java.logging.jul.LoggerLevelArgumentToMethodRecipes
- org.openrewrite.java.ChangeMethodTargetToStatic:
methodPattern: java.util.logging.Logger getLogger(..)
fullyQualifiedTargetTypeName: org.apache.logging.log4j.LogManager
- org.openrewrite.java.ChangeMethodName:
methodPattern: java.util.logging.Logger config(..)
newMethodName: info
- org.openrewrite.java.ChangeMethodName:
methodPattern: java.util.logging.Logger fine(..)
newMethodName: debug
- org.openrewrite.java.ChangeMethodName:
methodPattern: java.util.logging.Logger finer(..)
newMethodName: trace
- org.openrewrite.java.ChangeMethodName:
methodPattern: java.util.logging.Logger finest(..)
newMethodName: trace
- org.openrewrite.java.ChangeMethodName:
methodPattern: java.util.logging.Logger severe(..)
newMethodName: error
- org.openrewrite.java.ChangeMethodName:
methodPattern: java.util.logging.Logger warning(..)
newMethodName: warn
- org.openrewrite.java.logging.log4j.ConvertJulEntering
- org.openrewrite.java.logging.log4j.ConvertJulExiting
- org.openrewrite.java.ChangeType:
oldFullyQualifiedTypeName: java.util.logging.Logger
newFullyQualifiedTypeName: org.apache.logging.log4j.Logger
- org.openrewrite.java.logging.ChangeLombokLogAnnotation:
loggingFramework: Log4j2
Usage
This recipe has no required configuration options. It can be activated by adding a dependency on org.openrewrite.recipe:rewrite-logging-frameworks
in your build file or by running a shell command (in which case no build changes are needed):
- Gradle
- Gradle init script
- Maven POM
- Maven Command Line
- Moderne CLI
- Add the following to your
build.gradle
file:
plugins {
id("org.openrewrite.rewrite") version("6.28.1")
}
rewrite {
activeRecipe("org.openrewrite.java.logging.log4j.JulToLog4j")
setExportDatatables(true)
}
repositories {
mavenCentral()
}
dependencies {
rewrite("org.openrewrite.recipe:rewrite-logging-frameworks:2.17.1")
}
- Run
gradle rewriteRun
to run the recipe.
- Create a file named
init.gradle
in the root of your project.
initscript {
repositories {
maven { url "https://plugins.gradle.org/m2" }
}
dependencies { classpath("org.openrewrite:plugin:6.28.1") }
}
rootProject {
plugins.apply(org.openrewrite.gradle.RewritePlugin)
dependencies {
rewrite("org.openrewrite.recipe:rewrite-logging-frameworks:2.17.1")
}
rewrite {
activeRecipe("org.openrewrite.java.logging.log4j.JulToLog4j")
setExportDatatables(true)
}
afterEvaluate {
if (repositories.isEmpty()) {
repositories {
mavenCentral()
}
}
}
}
- Run the recipe.
gradle --init-script init.gradle rewriteRun
- Add the following to your
pom.xml
file:
<project>
<build>
<plugins>
<plugin>
<groupId>org.openrewrite.maven</groupId>
<artifactId>rewrite-maven-plugin</artifactId>
<version>5.46.1</version>
<configuration>
<exportDatatables>true</exportDatatables>
<activeRecipes>
<recipe>org.openrewrite.java.logging.log4j.JulToLog4j</recipe>
</activeRecipes>
</configuration>
<dependencies>
<dependency>
<groupId>org.openrewrite.recipe</groupId>
<artifactId>rewrite-logging-frameworks</artifactId>
<version>2.17.1</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
</project>
- Run
mvn rewrite:run
to run the recipe.
You will need to have Maven installed on your machine before you can run the following command.
mvn -U org.openrewrite.maven:rewrite-maven-plugin:run -Drewrite.recipeArtifactCoordinates=org.openrewrite.recipe:rewrite-logging-frameworks:RELEASE -Drewrite.activeRecipes=org.openrewrite.java.logging.log4j.JulToLog4j -Drewrite.exportDatatables=true
You will need to have configured the Moderne CLI on your machine before you can run the following command.
mod run . --recipe JulToLog4j
If the recipe is not available locally, then you can install it using:
mod config recipes jar install org.openrewrite.recipe:rewrite-logging-frameworks:2.17.1
See how this recipe works across multiple open-source repositories
Run this recipe on OSS repos at scale with the Moderne SaaS.
The community edition of the Moderne platform enables you to easily run recipes across thousands of open-source repositories.
Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.
Data Tables
Source files that had results
org.openrewrite.table.SourcesFileResults
Source files that were modified by the recipe run.
Column Name | Description |
---|---|
Source path before the run | The source path of the file before the run. null when a source file was created during the run. |
Source path after the run | A recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run. |
Parent of the recipe that made changes | In a hierarchical recipe, the parent of the recipe that made a change. Empty if this is the root of a hierarchy or if the recipe is not hierarchical at all. |
Recipe that made changes | The specific recipe that made a change. |
Estimated time saving | An estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds. |
Cycle | The recipe cycle in which the change was made. |
Source files that errored on a recipe
org.openrewrite.table.SourcesFileErrors
The details of all errors produced by a recipe run.
Column Name | Description |
---|---|
Source path | The file that failed to parse. |
Recipe that made changes | The specific recipe that made a change. |
Stack trace | The stack trace of the failure. |
Recipe performance
org.openrewrite.table.RecipeRunStats
Statistics used in analyzing the performance of recipes.
Column Name | Description |
---|---|
The recipe | The recipe whose stats are being measured both individually and cumulatively. |
Source file count | The number of source files the recipe ran over. |
Source file changed count | The number of source files which were changed in the recipe run. Includes files created, deleted, and edited. |
Cumulative scanning time | The total time spent across the scanning phase of this recipe. |
99th percentile scanning time | 99 out of 100 scans completed in this amount of time. |
Max scanning time | The max time scanning any one source file. |
Cumulative edit time | The total time spent across the editing phase of this recipe. |
99th percentile edit time | 99 out of 100 edits completed in this amount of time. |
Max edit time | The max time editing any one source file. |
Contributors
Piotr P. Karwasz, Tim te Beek, Tim te Beek, Jonathan Schnéider