[jira] [Commented] (GERONIMO-5996) Development mode for Aries applications

["Jarek Gawor (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GERONIMO-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045075#comment-13045075 ] 

Jarek Gawor commented on GERONIMO-5996:
---------------------------------------

Committed a set of changes in revision 1132745 that allow an Aries application to be re-resolved each time it is started. This feature is enabled once the "org.apache.geronimo.aries.resolveApplicationOnDeploy" system property is set to "false". That means, that during initial deployment of the application it won't be resolved and DEPLOYMENT.MF won't be generated & stored. And so each time the application is started and there is no DEPLOYMENT.MF the application will be re-resolved to generate a temporary in-memory only DEPLOYMENT.MF.


> Development mode for Aries applications
> ---------------------------------------
>
>                 Key: GERONIMO-5996
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5996
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Aries
>    Affects Versions: 3.0
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>
> Right now during Aries application deployment the application is resolved (if it wasn't before) - the DEPLOYMENT.MF is generated. At runtime the DEPLOYMENT.MF information is used to provision the bundles with the exact versions. In production this makes sense as we want to have the same set of bundles wherever the application is running. However, during deployment this behavior might not be desirable. At deployment time one might want to pick up the latest & greatest bundles without re-deploying the whole application.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira