I agree with any solution, but I have no idea how to implement it.
If we do not include the uberjar as the Maven2 plugin's dependency,
we run into two problems:
The Maven2 plugin would need to depend on each and every
container we have. And, if a new container is added, we'd need
to add it in two different locations. Not good.
The integration tests on containers are executed with the
uberjar, and this for all containers. Hence, the same would need
to be rewritten for the Maven2 plugin and for each container,
which in my opinion just doubles the effort unnecessarily.