[ISSUE-103]: Migrate away from log4j 1.x #104
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ISSUE-103
Description of the fix:
The following points were considered before coming up with the solution:
Solution:
As an overall solution to fix log4j related vulnerabilities, i have updated the log4j package to recent stable 2.x version. This migration document provided by the official website was used as an overall reference.
File changes made
Added
Changed
Logger.getLogger
command withLogManager.getLogger
command in classes belonging toapps/sparkpost-samples-app/src/main/java/com/sparkpost
package.Logger.getRootLogger().setLevel
command withConfigurator.setRootLevel
command upon migration in all of the BeforeClass methods in the integration tests and in classes belonging toapps/sparkpost-samples-app/src/main/java/com/sparkpost
package.BasicConfigurator.configure()
command withConfigurator.initialize(new DefaultConfiguration())
command in helpers/SparkPostBaseApp.java file.Testing done
mvn clean install
command runs successfully and tests are all passing on migration