Hi Matt, That's normal thinking IMO not devil's advocacy :-) The JDK provides a bare bones extension mechanism in the service loader but that's not enough for a real plugin system.
Gary On Tue, Apr 12, 2022, 11:30 Matt Benson <mben...@apache.org> wrote: > Devil's advocate thought: given that Commons, while not officially limited > to such, has heretofore concentrated on the Java ecosystem; as the core JDK > evolves, matures and provides more and more functionality out of the box, > possibly Commons components would have to increase in complexity to be able > to provide anything worthwhile. > > Matt > > On Tue, Apr 12, 2022, 7:53 AM Gilles Sadowski <gillese...@gmail.com> > wrote: > > > Le mar. 12 avr. 2022 à 13:23, Gary Gregory <garydgreg...@gmail.com> a > > écrit : > > > > > > Commons Component can and do depend on other runtime libraries, for > > > example, VFS, Configuration, JCS, and so on. There are libraries that > are > > > naturally lower level where we do want to keep zero depencies like IO > and > > > Lang. If an app has a plugin system it seems evident to me that it > would > > be > > > the kind of app that depends on other libraries anyway. > > > > Question remains: Start something here or not (advantages vs drawbacks)? > > > > > > > > Gary > > > > > > On Tue, Apr 12, 2022, 05:57 Gilles Sadowski <gillese...@gmail.com> > > wrote: > > > > > > > Hello. > > > > > > > > Le mar. 12 avr. 2022 à 08:58, Romain Manni-Bucau > > > > <rmannibu...@gmail.com> a écrit : > > > > > > > > > > Sounds like https://svn.apache.org/repos/asf/commons/sandbox/ can > > be a > > > > > ready to start place even if I still think incubator is the real > > place > > > > for > > > > > such a project since it will quickly overpass commons standard case > > with > > > > a > > > > > lot of modules if it gets a community and adopted (for > integrations). > > > > > > > > > > > > > "Commons" components are supposed to not depend on anything > > > > (except other "Commons" components and optional dependencies). > > > > If some of them need the functionality being discussed in this thread > > > > (as has been mentioned by Matt S, Matt J and Gary), but it is defined > > > > in another TLP, reuse will be "forbidden". > > > > > > > > A modular (maven) project could contain > > > > * modules that abide by the "no-dependency" policy (providing "core" > > > > functionality that can be reused here), and > > > > * modules with external dependencies whenever required. > > > > [If the latter modules are considered out-of-scope for Commons, then > > > > the glue code would be left for the respective projects to > implement.] > > > > > > > > Regards, > > > > Gilles > > > > > > > > >> [...] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > >