Re: [DISCUSS] Feature branch to update a nodetool obsolete dependency (airline)

2024-07-08 Thread Caleb Rackliffe
This thread is clearly mostly not about the feature branch question, but sure...let's summarize the case for picocli (rather than airline-2, jcommander, and commons-cli) in a fresh, specifically titled thread. Then we can continue any library-agnostic discussion here if necessary. On Mon, Jul 8, 2

Re: [DISCUSS] Feature branch to update a nodetool obsolete dependency (airline)

2024-07-08 Thread Brad
Many of the utilities in the tools directory (BulkLoader, SSTableExpoert, etc) already use apache.commons.cli. On Mon, Jul 8, 2024 at 4:28 PM Dinesh Joshi wrote: > I agree about picking libraries on their merit but a major factor for any > open source project should consider today is the possibi

Re: [DISCUSS] Feature branch to update a nodetool obsolete dependency (airline)

2024-07-08 Thread Dinesh Joshi
I agree about picking libraries on their merit but a major factor for any open source project should consider today is the possibility of unfavorable/hostile licensing changes. On Mon, Jul 8, 2024 at 1:15 PM Jon Haddad wrote: > Without getting into the pros and cons of both libraries, I have to

Re: [DISCUSS] Feature branch to update a nodetool obsolete dependency (airline)

2024-07-08 Thread Jon Haddad
Without getting into the pros and cons of both libraries, I have to point out there's something unsettling about making decisions about libraries we used based on arbitrary rules an employer has put into place on its employees. The project isn't governed by Apple, it's governed by individual contr

Re: [DISCUSS] Feature branch to update a nodetool obsolete dependency (airline)

2024-07-08 Thread Dinesh Joshi
I agree, having a DISCUSS thread with a specific subject line is less likely to be overlooked. One thing I'd like to note here is PicoCLI and Airline 2 are independent projects that are ALv2 licensed. A subset of the Cassandra contributors may have difficulty contributing to such projects due to p

Re: [DISCUSS] Feature branch to update a nodetool obsolete dependency (airline)

2024-07-08 Thread David Capwell
> I don't think that a separate thread would add extra visibility Disagree. This thread is about adding a feature branch, so many could ignore if they don’t care. The fact you are switching the library (and which one) is something we have to hunt for. By having a new DISCUSS thread it makes i

Re: [DISCUSS] Feature branch to update a nodetool obsolete dependency (airline)

2024-07-08 Thread Caleb Rackliffe
+1 on picocli RE the feature branch, I would just maintain the feature branch in your own fork to break out whatever "reviewable units" of code you want. When all the incremental review is done (I have no problem going back and forth), squash everything together, do whatever additional testing you