Hello,
Given the newly written JPAMailRepository (cf JAMES-2656) I propose to
remove (after a deprecation cycle) JDBCMailRepository.
Rationals:
- We now have a better alternative
- It's set up is undocumented, people that recently tried complained
- Reliance on Java serialization
- Creates confusion with other mail repositories.
- Several bugs are known: limits on attributes serialization, no null
sender support, amongst others
- Incurs a maintenance cost...
- Last meaningful contribution was 3 years ago.
Users relying on it can adopt the newly introduced JPAMailRepository.
Existing data can be migrated via re-processing (and a bit of dedicated
configuration).
Thoughts?
Best regards,
Benoit
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
