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 waynefay@gmail.com designates
 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+A8vzFPjRrjQ05O7vE8zZe6kFFvyCSkFpif1t6vypJrBQ-GoQ@mail.gmail.com>
References: 
 <CA+A8vzFPjRrjQ05O7vE8zZe6kFFvyCSkFpif1t6vypJrBQ-GoQ@mail.gmail.com>
From: Wayne Fay <waynefay@gmail.com>
Date: Sun, 6 May 2012 14:04:19 -0500
Message-ID: 
 <CALy+7U=iZ9F5SiQB2+LivKsavt1jV5WZ+MH+a1x__dYtHNSp2Q@mail.gmail.com>
Subject: Re: including src/main/webapp with maven-shade-plugin plugin
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=UTF-8

> Is there any way to include the default src/main/webapp into the output of
> the uber jar generated by the maven-shade-plugin?
> As it stands now, I'm only getting src/main/resources, and I'd rather not
> move src/main/webapp into src/main/resources.

Use build-helper-maven-plugin to add this resource path to the build.

But I think you are probably misusing or abusing the shade plugin.

Why don't you describe the real use case in more detail?

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org