Uploaded image for project: 'Maven Shade Plugin'
  1. Maven Shade Plugin
  2. MSHADE-42

Reactor builds do not use shaded jar

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 1.1
    • None
    • None

    Description

      I have a multi-module project with several of the modules using shade to create uber jars.

      One the modules depends on an uber jar module. When doing a reactor build, this module is built with a compile classpath containing:
      /xxx/yyy/uberjar-module/target/classes
      rather than the shaded uber jar created (and installed) earlier in the reactor build.

      When the module is built alone, the dependency in the compile classpath is correctly the shaded jar in the local repository.

      I don't know enough about the internals of reactor builds to determine if this is a deficiency of the shade plugin or Maven's reactor mechanism.

      Attachments

        1. MSHADE-42.patch
          3 kB
          james.w.dumay
        2. MSHADE-42-alternate.diff
          0.6 kB
          Brett Porter

        Issue Links

          Activity

            People

              brett Brett Porter
              sprynter David Meibusch
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: