Skip to content

Conversation

cwperks
Copy link
Member

@cwperks cwperks commented Sep 3, 2025

Description

Replace commons-lang:commons-lang with org.apache.commons:commons-lang3

Related Issues

commons-lang is not maintained and has moved to commons-lang3 per maven central: https://mvnrepository.com/artifact/commons-lang/commons-lang

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@cwperks cwperks requested review from peternied and a team as code owners September 3, 2025 16:59
Signed-off-by: Craig Perkins <[email protected]>
Copy link
Contributor

github-actions bot commented Sep 3, 2025

❌ Gradle check result for 95b5c99: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Sep 3, 2025

❌ Gradle check result for 95b5c99: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Comment on lines +14 to +17
/**
* Minimal shim to satisfy Azure Classic which expects commons-lang 2.x.
* Delegates to commons-lang3.
*/
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thoughts on this? It creates a shim around StringUtils from commons-lang3 that spoofs that this is coming from commons-lang:commons-lang. The alternative is upgrading azure deps, but that is non-trivial.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This appears to be the azure dependency this plugin is using? Which is from February 2016? Adding this StringUtils wrapper hardly seems like the biggest problem here...

Copy link
Member Author

@cwperks cwperks Sep 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its a non-trivial update. How do you think the upgrade should be handled?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was more leaning towards deprecating this plugin for future removal :)

It appears to be using the "classic" Azure APIs. I think the ideal solution would be to replace this plugin with a plugin that uses modern Azure APIs (assuming this is need for an Azure discovery plugin at all, of course).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would definitely support taking it out of the core repo and create a separate repo as #17246 proposed.

Copy link
Contributor

github-actions bot commented Sep 3, 2025

❌ Gradle check result for bb27409: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Sep 3, 2025

❌ Gradle check result for bb27409: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Sep 4, 2025

❌ Gradle check result for bb27409: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Sep 4, 2025

❌ Gradle check result for bb27409: null

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Sep 4, 2025

❌ Gradle check result for bb27409: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Sep 4, 2025

❌ Gradle check result for bb27409: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Sep 4, 2025

❌ Gradle check result for 6c3c7f7: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Sep 4, 2025

✅ Gradle check result for 6c3c7f7: SUCCESS

Copy link

codecov bot commented Sep 4, 2025

Codecov Report

❌ Patch coverage is 0% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 72.93%. Comparing base (3e747cb) to head (6c3c7f7).

Files with missing lines Patch % Lines
...main/java/org/apache/commons/lang/StringUtils.java 0.00% 10 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               main   #19229      +/-   ##
============================================
+ Coverage     72.79%   72.93%   +0.14%     
- Complexity    69605    69722     +117     
============================================
  Files          5658     5659       +1     
  Lines        320079   320089      +10     
  Branches      46345    46345              
============================================
+ Hits         232996   233462     +466     
+ Misses        68230    67718     -512     
- Partials      18853    18909      +56     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants