-
Notifications
You must be signed in to change notification settings - Fork 994
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
PHOENIX-6349 Add and use commons-cli to phoenix-thirdparty #1122
Conversation
💔 -1 overall
This message was automatically generated. |
Is it possible to write an enforcer rule to prevent imports of the non-shaded commons-cli packages? I think HBase has something you can copy (if you don't already know how to do this off the top of your head) |
This is a test version that depends on phoenix-thirdparty 1.1.0-SNAPSHOT
Yes, Viraj has just added the feature a few weeks ago. |
💔 -1 overall
This message was automatically generated. |
@@ -82,7 +82,7 @@ | |||
<hadoop.version>3.1.4</hadoop.version> | |||
<hbase.thirdparty.version>2.2.1</hbase.thirdparty.version> | |||
|
|||
<phoenix.thirdparty.version>1.0.0</phoenix.thirdparty.version> | |||
<phoenix.thirdparty.version>1.1.0-SNAPSHOT</phoenix.thirdparty.version> |
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.
we will replace the release version after the phoenix 3rd party release right?
should we wait and then merge this?
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.
We shouldn't release 4.16/5.1with snapshot dependecies.
We can either merge this now, and update when we release thirdparty 1.1.0, or we can wait with the merge until we have 1.1.0 final.
I'm going to prepare an rc0 for thirdparty this weekend.
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.
@stoty if it follows the same step, I can release the thirdparty this in my time zone today.
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 will do publish rc0 and send out the mail in an hour.
According to the ASF rules, we must leave at least 72 hours for a release vote.
If we take that literally, and count the weekend in, then we can do the official release on Monday afternoon PT.
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.
sounds great! Thanks again for the contribution!
💔 -1 overall
This message was automatically generated. |
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 (non-binding), only pending change is dropping -SNAPSHOT after release
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 (belated)
This is an test version the finle one needs to set thirdpart-version to 1.1.0