Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of ekoifman@hortonworks.com
 designates 209.85.217.180 as permitted sender)
MIME-Version: 1.0
Date: Mon, 14 Jul 2014 10:53:32 -0700
Message-ID: 
 <CAG0AUg1p76NL4WPPCkBg-U+wXf_TDxotXrzprGp29F-C0_J_Fg@mail.gmail.com>
Subject: maven shade/artifact naming help
From: Eugene Koifman <ekoifman@hortonworks.com>
To: users@maven.apache.org
Content-Type: multipart/alternative; boundary=001a113364202a541504fe2af8e7

--001a113364202a541504fe2af8e7
Content-Type: text/plain; charset=UTF-8

Hi,
I have an existing multi-module project.  A module A (i.e. artifactId=A)
uses shade plugin to create an uber jar.  The shade plug in config doesn't
retain the original (slim) jar so the only artifact produced/published from
this module is A.jar which is the uber jar.

Now I need to produce a 'slim' jar (lets call it A-core.jar) which only has
the classes from module A.   Since this was set up several releases ago I
have to keep A.jar as a fat jar to preserve backwards compatibility.

(I can easily make shade produce A.jar as the thin jar and A-uber.jar (or
any other name) as the fat jar, but this is not acceptable.)

Is there some way to make shade plug in do that?
-- 

Thank youm,
Eugene

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

--001a113364202a541504fe2af8e7--