Return-Path: X-Original-To: apmail-geronimo-dev-archive@www.apache.org Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB15E4616 for ; Wed, 29 Jun 2011 09:24:32 +0000 (UTC) Received: (qmail 92334 invoked by uid 500); 29 Jun 2011 09:24:32 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 92227 invoked by uid 500); 29 Jun 2011 09:24:31 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 90214 invoked by uid 99); 29 Jun 2011 09:24:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2011 09:24:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2011 09:24:10 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id F0D3B439BB1 for ; Wed, 29 Jun 2011 09:23:28 +0000 (UTC) Date: Wed, 29 Jun 2011 09:23:28 +0000 (UTC) From: "Shawn Jiang (JIRA)" To: dev@geronimo.apache.org Message-ID: <1911074682.1822.1309339408983.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <513628260.34442.1306070027396.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Resolved] (GERONIMO-5968) To support module priority so that we could control the sub-modules handling sequence during the deployment process. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/GERONIMO-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-5968. ----------------------------------- Resolution: Fixed Fix Version/s: 3.0 fixed with trunk#1126451 > To support module priority so that we could control the sub-modules handling sequence during the deployment process. > -------------------------------------------------------------------------------------------------------------------- > > Key: GERONIMO-5968 > URL: https://issues.apache.org/jira/browse/GERONIMO-5968 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment > Affects Versions: 3.0 > Reporter: Shawn Jiang > Assignee: Shawn Jiang > Fix For: 3.0 > > > Currently, if there are no module info in application DD, we scan the zip entries in ear to determine what are the modules included in EAR. And the sub-moudles sequence is based on the sequence the modules were deteceted. > But, sometime, we definitely want the modules building in a given sequence because one module building might need other module's building result. > Following sub module handling sequence would be a good: > 1, ConnectorModule > 2, EjbModule > 3, WebModule > 4, AppClientModule -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira