Maven WAR Plugin (moved to ASF)
  1. Maven WAR Plugin (moved to ASF)
  2. MWAR-178

war plugin documentation and probably implementation is unaware of javaee 5

    Details

    • Type: New Feature New Feature
    • 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 :
      0

      Description

      The example I'm aware of:
      http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html talks about using the war's manifest.mf classpath to include jars in the ear in the war module's classloader. In ee5, there's a ear lib directory: everything in that is automatically included in the ear level classloader, which is certainly available to every war, most likely by being a parent classloader to the war classloader. One consequence of this is that using the manifest classpath in a 1.4 container will likely result in each war getting separate copies of the lib jar classes whereas the ee5 lib directory will result in shared classes.

        Activity

        Hide
        Stéphane Nicoll added a comment -

        isn't it a candidate for the ear plugin instead? How would you resolve this issue?

        Show
        Stéphane Nicoll added a comment - isn't it a candidate for the ear plugin instead? How would you resolve this issue?
        Hide
        Karl Heinz Marbaise added a comment -

        If you have any objections don't hesitate to reopen the issue.

        Show
        Karl Heinz Marbaise added a comment - If you have any objections don't hesitate to reopen the issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            David Jencks
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: