Exclude commons-configuration - #4468
Conversation
Signed-off-by: ph33rtehgd <geedude@gmail.com>
|
Typically you'd create the PR against the lowest version branch and we would merge it forward. See also Netflix/eureka#1601 |
|
Unfortunately, running the build reveals So this will require a new release of eureka with my merged PR mentioned above |
|
@spencergibb Got it, apologies, this is the first time I've raised a PR against an open source project, I thought it might actually go the other way :) (master down to older branches). Do you want me to close this PR and open a new one starting at 4.2.x (or if there's a different branch that's lower and still supported I can start there)? As for the commons-lang change to no longer require ExceptionUtils in Eureka is needed. When I was testing out my change locally I had the latest Netflix 2.x branch checked out i n my workspace that already contained your PR merged locally so I didn't notice it. Hopefully since your change is minor on Eureka that can get released in the near future and then we can merge this change. |
There is indeed no fix for it from the Spring Cloud Netflix project. I tried the same where I work, but then I stumbled on the same issue and I had to add
|
|
This PR has been merged and we just need a release of eureka Netflix/eureka#1601 |
Just out of curiosity, why the string interpolation there has been replaced with |
|
Because the other doesn't take an exception as an argument |
Ehm, am I missing something? |
|
TIL. |
This PR is meant to primarily resolve this issue: #4446
My comments in the issue give some more detailed analysis, but from what I see is that while commons-configuration is used by eureka-client there isn't a flow through Spring Cloud Netflix that actually utilizes any classes from eureka-client that will actually utilize commons-configuration. Given this dependency's age, the fact that it's EOL and the fact the Netflix very likely won't be updating this I believe the most prudent thing to do is exclude this dependency as it should not negatively impact this Spring module.
It should also resolve this issue: #4457
I believe this should also be merged into the 4.2.x and 4.3.x branches. I can raise PRs for those too, if that's OK.