HI everyone,

we talked of it a lot but i only took some time to work on it this morning:
https://issues.apache.org/jira/browse/OPENJPA-2831

Dropped commons-collections4 from our stack (for now just copying the few
classes we use but it enables more easily drop code and abstractions we
don't use).

I suspect the next dependencies we can drop are serp and commons-logging,
then we would be "pure" (ie only depend on jpa spec and asm - not sure this
one can be dropped). Serp is "frozen" and should be replaced by direct asm
code but it requires some investment. Commons logging is easier to drop but
is a breaking change (in terms of config) we can desire to avoid so maybe
for next round ;).

Hope it makes sense.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>

Reply via email to