...

We don't know what will actually make it into the final release but take those things as moonshot ideas that i think are worth doing on the Pax Exam Platform.

Ease of Use

Clean-up API

The API contains many methods used in previous versions and should be cleaned up for easier use and more straigt forward implementation.

Cut-down Dependencies

Currently Pax Exam has a large dependecy chain, we should check if we can cut down this or at least make it more clear why we need a given dependency

Asciidoc User Manual

Confluence is not the best way to create and maintain our documentation. Other OPS4J projects have successfully moved to Asciidoc, and we should do the same for Pax Exam.

New APIs

Extension API

Currently only Test Containers are easy to add. Other parts of the Pax Exam System are very rigid and hard to extend. 

...

Clean-up API

The API contains many methods used in previous versions and should be cleaned up for easier use and more straigt forward implementation.

Cut-down Dependencies

Currently Pax Exam has a large dependecy chain, we should check if we can cut down this or at least make it more clear why we need a given dependency

Support for multiple (even non-test) Container in one Test/Suite/Module

Currently onyl only one testcontainer is allowed (or picked up). We should enable to allow a Per-Test (or even per test method) choice as we as support for Users to fire up additional containers (e.g. for client/server tests).

...