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
Warning to remove commons-logging.jar from classpath - Camunda 7.20-alpha4 #3673
Comments
Hi @amardeep2006, Thank you for reaching out to us with this and using our product. Could you please share a minimal example that reproduces the scenario? I suspect the Best regards, |
Thanks for your response @yanavasileva here is the output of command you suggested . I still don't see the commons-logging in my dependency tree . Please let me know if there is some other commands I should try. I can upload the project to GitHub to reproduce this . [INFO] |
@yanavasileva Update : I just looked at the Camunda Run distro logs and I see the same warning .
/ | __ _ _ __ ___ _ _ _ __ | | __ _ | _ | | __ | | / | ___ _ __ _ __ ___ | _ \ _ _ _ __ Spring-Boot: (v3.1.1) 2023-08-15T11:20:05.128+05:30 INFO 16588 --- [ main] org.camunda.bpm.run.CamundaBpmRun : Starting CamundaBpmRun v7.20.0-alpha4 using Java 17.0.7 with PID 16588 (C:\Users\amar\Downloads\camunda-bpm-run-7.20.0-alpha4\internal\camunda-bpm-run-core.jar started by amar in C:\Users\amar\Downloads\camunda-bpm-run-7.20.0-alpha4)
Deployment does not provide any case definitions.
2023-08-15T11:20:14.504+05:30 INFO 16588 --- [ main] org.camunda.bpm.application : ENGINE-07021 ProcessApplication 'invoiceProcessApplicationSpringBoot' registered for DB deployments [9af12326-3b2f-11ee-9046-02d49ed7fa2d, 99a7650c-3b2f-11ee-9046-02d49ed7fa2d]. Will execute process definitions
Deployment does not provide any case definitions. ... Now notifying creditor Bobby's Office Supplies 2023-08-15T11:20:17.467+05:30 INFO 16588 --- [ main] o.c.b.e.i.InvoiceApplicationHelper : Start 3 instances of Invoice Receipt, version 2 |
Hi @amardeep2006, I had a second look and saw the log, I overlooked it before that as it doesn't follow the logging pattern (you can see below that's printed with
That been said, no action is required from Camunda or user side, as you pointed out there's no Best regards, |
Hello, I am experiencing the same problem. |
@RalucaDiaconescu, you are right, nice catch. |
Hi all (/cc @RalucaDiaconescu), I revisited the topic again, summary:
As the shaded I would suggest two options, if users nevertheless would like get rid of the log:
Best, Internal notes for decision
|
Environment (Required on creation)
Spring boot 3.1.2
Camunda 7.20.0-alpha4
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
I have existing project on Camunda 7.19 . Now I have upgraded it to 7.20-alpha4 .
While building my project , I am seeing a warning in logs during unit tests execution.
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
Steps to reproduce (Required on creation)
Use Camunda starter based on Camunda-7.20.0-alpha-4
Observed Behavior (Required on creation)
Warning in logs : Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
Expected behavior (Required on creation)
Warning Should not be there
Root Cause (Required on prioritization)
Solution Ideas
Hints
Links
Breakdown
Pull Requests
Dev2QA handover
The text was updated successfully, but these errors were encountered: