In a multi-module setup, I am trying to build an EAR from a mix of projects for which I have the source code and a number of binary modules for which I do not have the source code. I have installed these binaries in my local M2 repository and reference them in various POMs. So far so good, but a number of these binaries are J2EE modules themselves, so they are also mentioned in the dependencies list in the POM of the EAR-project. Most of these modules contain a MANIFEST.MF file with a classpath entry that names the dependencies by their 'non-maven-name', i.e. X.jar instead of X-1.0.jar, and that obviously causes problems when these modules are deployed by the Application Server.
Thoughts anyone? Harry Klerks
