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

Code snippet of **_<org.apache.commons.logging.LogFactory: org.apache.commons.logging.LogFactory getFactory()>_** in _**org.slf4j:jcl-over-slf4j:jar:1.7.16:compile**_ (loaded version): #2395

Open
vangirja opened this issue Dec 15, 2022 · 7 comments
Labels
epic: dependencies info: help wanted status: stale issues and pull requests that have not had recent interaction type: refactoring

Comments

@vangirja
Copy link

    Code snippet of **_<org.apache.commons.logging.LogFactory: org.apache.commons.logging.LogFactory getFactory()>_** in _**org.slf4j:jcl-over-slf4j:jar:1.7.16:compile**_ (loaded version):

01

Code snippet of <org.apache.commons.logging.LogFactory: org.apache.commons.logging.LogFactory getFactory()> in commons-logging:commons-logging:jar:1.2:compile
(shadowed but expected to invoke method):
02
.......

As a result, these conflicting method included in commons-logging:commons-logging:jar:1.2:compile deals with different cases, which changes the control flows and data flows. So being forced to use these methods in org.slf4j:jcl-over-slf4j:jar:1.7.16:compile may lead to inconsisitent semantic behaviors.

Originally posted by @HelloCoCooo in #868 (comment)

@jatinsihag234
Copy link

anyone woring on this issue??

@iluwatar
Copy link
Owner

Not at the moment. Would like to to work on it @jatinsihag234?

@jatinsihag234
Copy link

Not at the moment. Would like to to work on it @jatinsihag234?

Yes sir i wanna work on it

@stale
Copy link

stale bot commented Feb 26, 2023

This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status: stale issues and pull requests that have not had recent interaction label Feb 26, 2023
@mohanaraosv
Copy link
Contributor

Please assign this to me.

@jatinsihag234
Copy link

Please assign this to me.

bro i forget my github id pass now i am free and active i am alread working on that

@stale stale bot removed the status: stale issues and pull requests that have not had recent interaction label Mar 6, 2023
@stale
Copy link

stale bot commented May 5, 2023

This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status: stale issues and pull requests that have not had recent interaction label May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic: dependencies info: help wanted status: stale issues and pull requests that have not had recent interaction type: refactoring
Projects
Development

No branches or pull requests

4 participants