• Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.3
    • Fix Version/s: 2.7
    • Labels:
    • Environment:
      mvn 2.0.5


      Provide a boolean configuration option for webModules to include the war's transitive dependencies.

      As described on it is very common in a J2EE environment to use so called skinny wars. Here the war's WEB-INF/lib will not contain the dependent jars, but instead they are packaged inside the EAR. The war references them through its META-INF/MANIFEST.MF

      This option could be used to avoid the 'painful part' mentioned in the above web page. The war's dependencies wouldn't have to be duplicated alongside the ear's.

      I also found an old issue (MEAR-14) which has asked for the current default behavior of not including the transitive dependencies. It suggests a property to include specific dependencies of the war. As far as I can tell this has never been implemented and this is also not what I am asking for. My proposal is an all of nothing kind of option for each war module in the ear.

      On a side note, for me this is the part where removal of the old maven 1 style properties per dependency is missed the most. With them it was possible to decide for each single dependency whether to put it in WEB-INF/lib or reference it through the manifest classpath. But of course, then we didn't have the transitive dependencies


        1. maven-ear-plugin-MEAR-60.patch
          43 kB
          Jeroen Ruijgers
        2. maven-ear-plugin-addon-1.0-SNAPSHOT-sources.jar
          1 kB
          Andreas Thaler
        3. maven-ear-plugin-addon-1.0-SNAPSHOT.jar
          3 kB
          Andreas Thaler

          Issue Links



              • Assignee:
       Dennis Lundberg
                mschutte Marcel Schutte
              • Votes:
                50 Vote for this issue
                25 Start watching this issue


                • Created: