Hello, I have a multimodule project with 2 modules: - an EJB project - an EAR project that only has the EJB as a dependency
When the EJB gets built, the indirect dependency to commons-lang gets resolved to version 2.0, and is hence referenced in the MANIFEST.MF Class-Path entry as commons-lang-2.0.jar The commons-lang dependency is an indirect dependency via 2 direct dependencies of the EJB. One uses version 2.1, whilst the other uses 2.0 Unfortunately, when the EAR file gets built, maven chooses to resolve commons-lang as version 2.1 and the EJB's Class-Path entry becomes inconsistent with the contents of the EAR. Is there any way to ensure consistency of the resolution process, other than managing the version via <dependencyManagement> after having detected the issue? (This is maven 2.0.9) Thanks in advance for your advice. -Olivier --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org