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 (asf.osuosl.org: domain of martijn.dashorst@gmail.com
 designates 64.233.166.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=aWqBt1SRzq2t2QWdYge+3/MxRtjgNycvG+CODoMdqT5TIQHEEguXBwoDMseFbaOIw3K1uP8xOFcMTo4QgiY7cIztCkac8IbuAQibr1t/MvNqJkW0jIA5ZSWNcYmeGr2blH2YvBx+pJp/fcwtUzRIDgObDmFd78OjXvlYVn9Db7Y=
Message-ID: <918312fe0606300840p2a22cfa7x68c64afd0c3e067a@mail.gmail.com>
Date: Fri, 30 Jun 2006 17:40:49 +0200
From: "Martijn Dashorst" <martijn.dashorst@gmail.com>
To: "Maven Users List" <users@maven.apache.org>
Subject: Re: Re: Assembly plugin with war packaging type fails to work
 properly
In-Reply-To: <44A48088.3090001@exist.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <918312fe0606291214k7c73a2c0tdc9b18363a61d4ae@mail.gmail.com>
	 <44A48088.3090001@exist.com>

I fixed this by forcing the assembly 2.0.1 version in the plugin
management section of my projects. The only thing that isn't solved by
that is that the assembly id is appended to the filename.

Martijn

On 6/30/06, Edwin Punzalan <epunzalan@exist.com> wrote:
>
> The only difference between assembly:assembly and assembly:attached is
> the object that they are working on.  The goal assembly:assembly uses
> ${executedProject} while assembly:attached uses ${project}.
>
> So if assembly:attached works for you, then I suggest you use it.
>
>
> Martijn Dashorst wrote:
> > All,
> >
> > We have an examples project which has an artifact type of 'war'. The
> > dependencies for the war are correct and for instance servlet api has
> > scope 'provided'.
> >
> > The provided jars don't show up in the WAR file, which is what I want.
> >
> > Now the catch: I want to create a combined src/binary ZIP distribution
> > using the assembly plugin that includes *ALL* dependencies such that
> > people can import the zip file as a complete eclipse, intellij Idea or
> > netbeans project without having to install maven, and download all
> > dependencies.
> >
> > However, what ever I specify in my assembly descriptor, only compile
> > time dependencies end up in the final zip.
> >
> > Is there any way to get this fixed? Can I override the dependency
> > resolver such that the assembly ignores everything the war type tells
> > it about dependencies?
> >
> > mvn clean site package assembly:attached
> >
> > seems to work. But I think the following should result in the same
> > packaging:
> >
> > mvn clean site assembly:assembly
> >
> > Any comments?
> >
> > Martijn
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

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