>The recent flip-flopping changes in [CLI] and [Configuration] [CLI] has zero runtime dependencies. Are test dependencies an issue from your POV?
> try to raise the question of when and how Commons components should depend on other Commons components. Some components are low-level like Lang and IO, while others sit higher, like VFS, Configuration, and Compress. I think it is normal for higher-level components to reuse lower-level building blocks, especially within our ecosystem. We also go outside Commons as well, for example: Compress depends on many third-party libraries to do its archiving and compression work: Zstd, Brotfi, and XZ. Lang has been justified since its inception as code low-level enough it could have been in the JDK itself. I include Lang in my projects and consider it part of the Java vocabulary. Over the years, features have crept into Lang that we now have deprecated and moved to Text. I am mindful of what belongs where. HTH, Gary On Fri, Oct 25, 2024 at 7:16 AM Gilles Sadowski <gillese...@gmail.com> wrote: > Hi. > > The recent flip-flopping changes in [CLI] and [Configuration] > made me wonder if I should, again, try to raise the question > of when and how Commons components should depend on > other Commons components. > > Previous attempts (hinting at "when" and "how") have been > ignored, but shouldn't we at least have a consensus, backed > with a few hard rules? > One such rule could be that if the minimum required JDK > provides functionality that is also implemented in a Commons > component, that component should > 1. call the JDK equivalent functionality, > 2. deprecate its (redundant) implementation > in order to encourage developers to use the JDK instead, and > allow us to trim down the Commons "bloat". > > WDYT? > > Regards, > Gilles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
