Norman Maurer deb90923a2 Ensure PooledByteBuf.initUnpooled(...) correctly set the allocator ... Motivation: Commit 8dda984afe introduced a regression which lead to the situation that the allocator is not set when PooledByteBuf.initUnpooled(...) is called. Thus it was possible that PooledByteBuf.alloc() returns null or the wrong allocator if multiple PooledByteBufAllocator are used in an application. Modifications: - Correctly set the allocator - Add test-case Result: Fixes [#6436].		2017-02-23 19:53:17 +01:00
..
src	Ensure PooledByteBuf.initUnpooled(...) correctly set the allocator	2017-02-23 19:53:17 +01:00
pom.xml	Only use Mockito for mocking.	2017-02-07 08:47:22 +01:00