-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Migrated commons-lang usages to commons-lang3 #17156
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
Conversation
looks great! I hope the tests will pass :) |
<dependency> | ||
<groupId>commons-lang</groupId> | ||
<artifactId>commons-lang</artifactId> | ||
<scope>provided</scope> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
drive by comment: i'm pretty sure it is important that these are marked as scope provided so the jars don't get duplicated by the extensions when building a distribution. That said, i could also be misremembering, please make sure that there are not multiple copies after this change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I build the package with -Pdist. I checked for commons-lang jar in the distribution
I can only find 2 instances
➜ apache-druid-32.0.0-SNAPSHOT git:(commons-lang3) find . -name "commons-lang-*.jar"
./extensions/druid-ranger-security/commons-lang-2.6.jar
./lib/commons-lang-2.4.jar
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are no places where only the scope
gets removed:
- all
pom.xml
changes are either remove the dep - there is one place where the dependency is upgraded from lang2 to lang3; but there are no scope changes there either
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is check failing with some license issue
it seems like extensions-core/druid-ranger-security
still refereces the old lib:
[INFO] org.apache.druid.extensions:druid-ranger-security:jar:32.0.0-SNAPSHOT
[INFO] +- org.apache.ranger:ranger-plugins-common:jar:2.4.0:compile
[INFO] | +- commons-lang:commons-lang:jar:2.6:compile
<dependency> | ||
<groupId>commons-lang</groupId> | ||
<artifactId>commons-lang</artifactId> | ||
<scope>provided</scope> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are no places where only the scope
gets removed:
- all
pom.xml
changes are either remove the dep - there is one place where the dependency is upgraded from lang2 to lang3; but there are no scope changes there either
Let me add back the license for commons-lang? It can be removed once the dependencies also migrate to commons-lang3. |
54b7784
to
33952af
Compare
there is no need to force-push the branch - the PR will be squashed in the end anyway. |
@shigarg1 it seems like you don't have any email addresses associated with you github account; so the system would use the noreply email address for the commit: Let me know if that's ok - or you could add one by following this guide |
@kgyrtkirk Updated the email. |
After some discussion with @clintropolis we've found that by fixing Druid to not use before/after commons-lang jar presences
parts of: mvn dependency:tree -pl sql
the retaining the new diff
proposed changes diff
taking a look at all the jars in the dist tgz (
|
Thank you @shigarg1! |
Issue Link - #17130