geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (GERONIMO-5968) To support module priority so that we could control the sub-modules handling sequence during the deployment process.
Date Wed, 29 Jun 2011 09:23:28 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shawn Jiang reassigned GERONIMO-5968:
-------------------------------------

    Assignee: Shawn Jiang

> 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

        

Mime
View raw message