Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: pass (hermes.apache.org: domain of jak-ant-user@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: user@ant.apache.org
From: Stephane Bailliez <sbailliez@apache.org>
Subject: Re: jboss tmp directory
Date: Sat, 20 Nov 2004 16:14:20 +0100
Lines: 25
Message-ID: <cnnn0g$vj7$1@sea.gmane.org>
References: <419CC0EA.8070508@tty.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
In-Reply-To: <419CC0EA.8070508@tty.nl>
Sender: news <news@sea.gmane.org>

Machiel Groeneveld wrote:
[...]
> The problem is (of course) that todir doesn't know how to resolve the 
> '*' and creates the dir *application.ear-contents.
> 
> I know this question has been asked before, but I couldn't find this 
> exact use case in the mailing list.

I would suggest you to do things differently.

Generally I have found it to be a good thing to have an exploded view of 
your ears and wars during the build process and simply war/ear it with 
different targets.

This is good to me because I have an exploded version of what's to be 
included (easier to look at) and this is good for the development 
process as well (redeploying even a moderate app can take minutes).

JBoss (like every app server I know) allows you to deploy an exploded 
version of an ear or war, therefore having a simple target that deploys 
(ie copy) the exploded version of the ear to your 
jboss.home/server/default/deploy or whatever will streamline things and 
you will be able to update your jsps without redeploying the whole app.

http://jboss.org/wiki/Wiki.jsp?page=ExplodedDeployment


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org