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

Improved logic for checking if log4j logback can be modified #1303

Closed
minwoo-jung opened this issue Dec 3, 2015 · 0 comments
Closed

Improved logic for checking if log4j logback can be modified #1303

minwoo-jung opened this issue Dec 3, 2015 · 0 comments
Assignees
Milestone

Comments

@minwoo-jung
Copy link
Member

Currently if application use old version for log4j or logback, print out log to can not modify class.
We add improve logic for checking if log4j logback can be modified. Because we imporve check logic, can not print out exception message.

@minwoo-jung minwoo-jung added this to the 1.5.2 milestone Dec 3, 2015
@minwoo-jung minwoo-jung self-assigned this Dec 3, 2015
@minwoo-jung minwoo-jung modified the milestones: 1.5.1, 1.5.2 Dec 4, 2015
@minwoo-jung minwoo-jung reopened this Dec 31, 2015
@minwoo-jung minwoo-jung modified the milestones: 1.5.2, 1.5.1 Dec 31, 2015
minwoo-jung added a commit to minwoo-jung/pinpoint that referenced this issue Dec 31, 2015
minwoo-jung added a commit that referenced this issue Dec 31, 2015
[#1303]Improved logic for checking if log4j logback can be modified
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant