The problem here is that WeldFilesDeployer.getClasspaths filters out the manifest referenced classpath, just because it is not contained inside the weld-translator.ear/weld-translator.jar archive. I commented out the filtering and no tests were broken.
That "fix" is committed along with a new testsuite test that reproduces the scenario above. Ales, do you remember for what reason WeldFilesDeployer was filtering the classpath entries? I need to know if I can delete that method or if it is needed for some specific scenario.
I think you're right -- the full classpath should be considered.
Filtering was more of a brain dump from some old code, which actually needed this filtering.
e.g. only valid classpath were the deployments paths, which is not the case here as your example shows it
I'll remove the unneeded code.