Hi! I see strange behavior when using the maven EAR plugin with the skinnyWar [1] feature, which might be a bug.
Here is the (simplified) module-structure I have: core +-- core-shared web +-- backend +-- war ee +-- ear Usually all modules share the same version (let's say 1.0) number. My "ear" module includes a skinny version of the war module, "core-shared" and some other 3rd-party dependencies. This works fine. However, when I update all modules to version 2.0-SNAPSHOT but keep the dependency on the "war" in the "ear" to version 1.0, the skinny war is no longer skinny. Instead the "war" 1.0 in the "ear" contains "core-shared" 1.0 dependency but the "ear" contains core-shared 2.0-SNAPSHOT. Thus, the dependency is included twice with different versions. IMHO the EAR plugin doesn't respect artifact's version information when removing JARs from the skinny war, but only removes JARs that match exactly (including version string). I'd consider this a bug. Or at least a missing feature in the EAR plugin. What do others think? Should I create a JIRA entry? thx, - martin [1] http://maven.apache.org/plugins/maven-ear-plugin/examples/skinny-wars.html
signature.asc
Description: PGP signature
