-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-16855. Changing wildfly dependency scope in hadoop-azure to compile #1929
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
|
💔 -1 overall
This message was automatically generated. |
|
Driver test results using accounts in Central India Account with HNS Support Account without HNS support |
snvijaya
left a comment
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.
+1
|
Plz add the description |
|
It's not mandatory for hadoop-azure though, is it? |
|
OK, I understand now; it's a regression from HADOOP-16346 -and the change spans hadoop-aws too, which now has acquired a mandatory dependency on wildfly -1 to this patch as is as we need something to cut out that wildfly jar dependency entirely I'll include this specific change in there so that you get it in your dependencies, even after we add some classloader resilience to wildfly use |
|
see #1948 I don't see that this is needed, as it should be propagating downstream. Have you been seeing this in trunk or elsewhere? Use mvn dependency:tree -Dverbose to get that dependency graph |

No description provided.