Hi developers, after working now for some time with M2, we run really in troubles with the M2 setup here. We use a company wide super POM and have a lot of multi module projects. Now after releasing some of the artifacts, we run into big trouble, since we had to detect, that the CLASSPATH does not match the dependencies in multi module builds (note, all modules build fine with the correct dependencies if Maven is started locally).
Problem: If a module references another one also part of the multi module build, a defined version is completely ignored building the CLASSPATH. Even if a module references a released version as dependency, the classpath will contain the other module as SNAPSHOT (MNG-2424). The situation is even worse if your module packages an EJB. In this case the manifest will contain the versions from the CLASSPATH, but not from the resolved dependencies (MEJB-18). Including such an EJB into an EAR will fail, because the bundled libs in the EAR correspond to the versions in the resolved dependencies, but not to the ones in the CLASSPATH i.e. the EJB is broken and cannot find its classpath elements from the manifest. This issue really kills our complete development environment, since you have to build either all those hundred artifacts individually or you have to release all of them everytime before you can test even a single one. And there's nothing you can configure in the POM to circumvent this. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
