Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Wed, 22 Jun 2011 14:54:47 +0000 (UTC)
From: "Jarek Gawor (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: 
 <1959127455.29606.1308754487542.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <956631127.1649.1307390339105.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (GERONIMO-5996) Development mode for Aries
 applications
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jarek Gawor resolved GERONIMO-5996.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0

> 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
>             Fix For: 3.0
>
>
> 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