Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 24643 invoked from network); 30 Jan 2008 06:00:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jan 2008 06:00:41 -0000 Received: (qmail 24805 invoked by uid 500); 30 Jan 2008 06:00:30 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 24781 invoked by uid 500); 30 Jan 2008 06:00:30 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 24770 invoked by uid 99); 30 Jan 2008 06:00:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2008 22:00:30 -0800 X-ASF-Spam-Status: No, hits=4.0 required=10.0 tests=DNS_FROM_OPENWHOIS,FORGED_YAHOO_RCVD,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2008 06:00:02 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JK5zV-0003B7-MQ for user@geronimo.apache.org; Tue, 29 Jan 2008 22:00:09 -0800 Message-ID: <15176087.post@talk.nabble.com> Date: Tue, 29 Jan 2008 22:00:09 -0800 (PST) From: Stuart Smith To: user@geronimo.apache.org Subject: Merging deployment plans MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: stuart_wildcat@yahoo.com X-Virus-Checked: Checked by ClamAV on apache.org I've been investigating some of the unique features that make Geronimo easier to use than JBoss. One of the features that has caught my attention is the ability to use external deployment information during the deployment process. What I'm wondering is if it is possible to have a deployment plan that is packaged with an application archive AND one that is external. I'm thinking anything that is always going to be the same can be in the internal deployment plan. Anything that may change from one environment to the next can be in the external plan. If this is possible would they be merged into a unified deployment plan during deployment? Would they be merged with one taking precedence over the other? Would one be completely ignored if the other is present? If this type of thing is possible it would be great, if not would it be possible to add? Many thanks for any replies. Thanks, Stuart -- View this message in context: http://www.nabble.com/Merging-deployment-plans-tp15176087s134p15176087.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.