[MSHADE-42] Reactor builds do not use shaded jar

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.1
• Assignee: Brett Porter
• Reporter: David Meibusch
• Created: 16/Sep/08 01:04
• Updated: 28/Dec/09 15:57
• Resolved: 24/Feb/09 07:09

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.

Issue Links

• is duplicated by: MSHADE-50 Shade relocate output jar not easily available to other modules in multi-module build
• is related to: MNG-2720 Multiproject dependencies not accurate for project.compileClasspathElements when run from root project
• is related to: MNG-3751 Multi-module project is non-deterministic in evaluating reactor artifacts defined as dependencies unless they are installed in the local repository