Hi, this use case sounds a bit strange ;-). You mean that your customer deploys the WAR to JBoss, and when deploying the WAR it is regenerated with a changed config? This is probably hardly possible, because JBoss would deploy the app another time when the new WAR is created, and thus your ant task is starting again. Why not providing your customer with an "installer", which runs ant and creates the WAR, a the WAR is finally copied to JBoss? Best regards Wolfgang View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215305#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...