Maven
  1. Maven
  2. MNG-3269

Different builds for ejb-client optional with parent

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: 2.0.7
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      4

      Description

      When trying to package a j2ee project's ejb-client artifact in the ear /lib directory the war plugin's optional attribute is ignored if building from the parent app project. If you build from the parent project you get the ejb-client packaged in the web-inf/lib directory. If you build the ejb, war, and ear independently you get the ejb-client packaged in the ear /lib directory. It seems when run from the parent project the dependency/artifact doesn't have the optional attribute set.

      Perhaps this is b/c the artifact is a project artifact that was attached from the ejb plugin it is not resolved as optional when the dependency is resolved from the war project.

      Attaching Geronimo's mytime sample with modifications to reproduce the behavior.

      1. MWAR114-maven-war-plugin-2.0.2.patch
        4 kB
        Tim Reilly
      2. MWAR114-maven-war-plugin-2.0.2.patch
        4 kB
        Tim Reilly
      3. MWAR114-maven-war-plugin-2.1-alpha-1.patch
        15 kB
        Tim Reilly

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Tim Reilly
          • Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: