Maven WAR Plugin
  1. Maven WAR Plugin
  2. MWAR-9

WAR plugin should support minimal WARs for inclusion within an EAR

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      1

      Description

      I noticed that when I build a WAR, I get a gigantic WEB-INF/lib with all my deps. This is fine for a default but maven should also support "skeleton" WARs which will be packaged within an EAR. We have EARs which package 3-4 WARs each and to have the deps duplicated within each WAR means we cannot have shared data (since the classes are loaded within each WAR's classloader, rather than by the parent EAR's classloader). It also means 80MB EARs!

      It seems like two things need to happen:

      1) Add a "skeleton" flag which prevents copying any dependencies to WEB-INF/lib.
      2) Instead generate a META-INF/MANIFEST.MF which has a Class-Path entry which lists the relative locations of the dependencies within the parent EAR.

      Fabrice has basically the same idea written down here. Starting with "- for a War..." : http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112737860024530&w=2

        Issue Links

          Activity

          Hide
          Barend Garvelink added a comment -

          This is a big issue for a lot of people, and the information on it appears to be very fragmented. I have tried to summarize all the information related to this issue on the Codehaus wiki so that a good, lasting solution can hopefully be found. Please chip in with your thoughts:

          http://docs.codehaus.org/display/MAVENUSER/Solving+the+Skinny+Wars+problem

          Show
          Barend Garvelink added a comment - This is a big issue for a lot of people, and the information on it appears to be very fragmented. I have tried to summarize all the information related to this issue on the Codehaus wiki so that a good, lasting solution can hopefully be found. Please chip in with your thoughts: http://docs.codehaus.org/display/MAVENUSER/Solving+the+Skinny+Wars+problem
          Hide
          Nicolas Marcotte added a comment - - edited

          Oups wrong ticket please delete the attached file

          Show
          Nicolas Marcotte added a comment - - edited Oups wrong ticket please delete the attached file
          Hide
          Dennis Lundberg added a comment -

          I would like to close this issue as "Won't fix".

          The proper way to solve this is in the EAR Plugin, like the proposals in MEAR-60 and MEAR-87.

          Show
          Dennis Lundberg added a comment - I would like to close this issue as "Won't fix". The proper way to solve this is in the EAR Plugin, like the proposals in MEAR-60 and MEAR-87 .
          Hide
          Nicolas Marcotte added a comment -

          As a maven user and in house plugins developer I wholeheartedly agree. However i would still like to see my updated test and documentations for MWAR-81 included as a stop gap measure.

          If my last patch to MWAR-81 is included I can document it on the cited wiki, tell the readers to subscribe to MEAR-60 and MEAR-87 for a correct solution while using MWAR-81 while we wait while proper patch is developed.

          However, I won't update the wiki if MWAR-81 is not included because if there are no test nor documentation on that functionality, it can disappear in any future release and it is a behaviour that would I dislike to see as a maven user and evangelist 1 !

          1. I may have drunk to much Koolaid but,hey!, your maven Koolaid taste so good.
          Show
          Nicolas Marcotte added a comment - As a maven user and in house plugins developer I wholeheartedly agree. However i would still like to see my updated test and documentations for MWAR-81 included as a stop gap measure. If my last patch to MWAR-81 is included I can document it on the cited wiki, tell the readers to subscribe to MEAR-60 and MEAR-87 for a correct solution while using MWAR-81 while we wait while proper patch is developed. However, I won't update the wiki if MWAR-81 is not included because if there are no test nor documentation on that functionality, it can disappear in any future release and it is a behaviour that would I dislike to see as a maven user and evangelist 1 ! I may have drunk to much Koolaid but,hey!, your maven Koolaid taste so good.
          Hide
          Dennis Lundberg added a comment -

          MWAR-81 will be included in the next WAR Plugin release.

          Show
          Dennis Lundberg added a comment - MWAR-81 will be included in the next WAR Plugin release.

            People

            • Assignee:
              Unassigned
              Reporter:
              Mike Perham
            • Votes:
              59 Vote for this issue
              Watchers:
              47 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: