vttran
vttran
Regarding the Resource leak detected at `MemoryMailRepositoryTest`, I tried to manually dispose of resources, but then the source code of the unit test look very noisy. IMO, disabling leak detection...
Many classes have been detected resource leaked. Almost come from unit-test, when it created new MailImpl for testing. Any other way is better than override detect mode everywhere?
> Is there any plan to carry on this work? Not yet, should we create a Jira task, then add it to the backlog, and close this pr?
Remark: - James is not supporting the extension for `Task json dto`. - We cannot declare Guice inject for `webadmin-dto` by normal way: ``` @Named(DTOModuleInjections.WEBADMIN_DTO) @ProvidesIntoSet public AdditionalInformationDTOModule
> What do you mean don't allow the use of the routes for now??? yes, because we can't start James. @chibenwa opinion ``` That's not possible yet... - 1. for...
We already have manually `docker-compose-distributed.yml` Should we still have a deployment test?
> @vttranlina needs a rebase :) I tried to rebase, but this pr depends on many other pr. It has a bit complex to rebase & resolve. So, I will...
After fixing the typo, we will get ci fail. Maybe it is related https://github.com/apache/james-project/pull/940#issuecomment-1085518526
On my PC 