shibboleth-dev - Re: distcopy target in build.xml
Subject: Shibboleth Developers
List archive
- From: Tom Scavo <>
- To: Walter Hoehn <>
- Cc: Howard Gilbert <>,
- Subject: Re: distcopy target in build.xml
- Date: Thu, 19 May 2005 15:05:29 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=swn2/c4sikO+HgqfU7PRSlZp20jPPJMJtiBdFj3cBkb3BSXcb+e3QX9mOKx51TkaoZHybtBDKGxN1vILKGynECWABunl8GAIjbJmS+3ThyS5wcXT2GVWJ07XKsZp7L+CGKPyvBXeibEVxGsaLDpjZE1YRk7gKrvElwYocqAJjF8=
On 5/19/05, Walter Hoehn
<>
wrote:
> An assumption was always made about the deployment descriptor, since
> "distcopy" was only meaningful if one had already used the other
> tasks to generate a war.
True.
> You can definitely modify the descriptor template, or we could make
> another variable that points to some other template.
At this point I can't comment one way or the other since I'm still
trying to understand the new build process and how it impacts what I'm
doing.
Tom
- distcopy target in build.xml, Andrew Booth, 05/18/2005
- RE: distcopy target in build.xml, Howard Gilbert, 05/18/2005
- Re: distcopy target in build.xml, Tom Scavo, 05/18/2005
- Re: distcopy target in build.xml, Walter Hoehn, 05/19/2005
- Re: distcopy target in build.xml, Tom Scavo, 05/19/2005
- Re: distcopy target in build.xml, Walter Hoehn, 05/19/2005
- Re: distcopy target in build.xml, Tom Scavo, 05/19/2005
- Re: distcopy target in build.xml, Walter Hoehn, 05/19/2005
- Re: distcopy target in build.xml, Tom Scavo, 05/19/2005
- Re: distcopy target in build.xml, Walter Hoehn, 05/19/2005
- Re: distcopy target in build.xml, Tom Scavo, 05/19/2005
- RE: distcopy target in build.xml, Howard Gilbert, 05/18/2005
Archive powered by MHonArc 2.6.16.