No objections from me. I'm +1 to normally killing old code too, but I think in this case it might be simple to keep both working in [configuration] as users appear to be still transitioning JEE apps to the jakarta namespace. We might just need to remember to remove the old package/namespace when we are certain a vast majority of users have migrated to jakarta.
Sorry for the radio silence in that PR, and thanks for taking over Matt! 🎉 -Bruno On Sun, 12 Jun 2022 at 10:26, Matt Juntunen <matt.a.juntu...@gmail.com> wrote: > I'm glad I asked this question :-) Bruno actually submitted a PR with > support for both the old and new namespaces [1] but we decided not to > go with it since it felt like too much to support both versions of the > API. However, this discussion is making me rethink that choice. For > one, dropping support for the old API may actually require users to > update their code (as described in my initial email), effectively > breaking backwards compatibility. However, we do want to support the > newer mailapi version as well so we do not force users to use an > outdated dependency. > > So, unless anyone objects, I will plan on resurrecting Bruno's PR > within the next few days and merging it in. > > Regards, > Matt J > > > [1] https://github.com/apache/commons-configuration/pull/107 > > On Fri, Jun 10, 2022 at 4:32 PM Emmanuel Bourg <ebo...@apache.org> wrote: > > > > On 10/06/2022 22:16, Rob Spoor wrote: > > > Since reflection is used to create the instances, isn't it possible to > > > support both? > > > > +1, we should support both > > > > Emmanuel Bourg > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
