Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <16793388.1146167618009.JavaMail.jira@brutus>
Date: Thu, 27 Apr 2006 19:53:38 +0000 (GMT+00:00)
From: "Aaron Mulder (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-1174) Hot deployer should know when a
 file was last deployed
In-Reply-To: <641711160.1132033467910.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-1174?page=all ]

Aaron Mulder updated GERONIMO-1174:
-----------------------------------

    Fix Version: 1.1
                     (was: 1.2)
      Assign To: Aaron Mulder
       Priority: Critical  (was: Major)

> Hot deployer should know when a file was last deployed
> ------------------------------------------------------
>
>          Key: GERONIMO-1174
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1174
>      Project: Geronimo
>         Type: Improvement
>     Security: public(Regular issues) 
>   Components: Hot Deploy Dir
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Critical
>      Fix For: 1.1

>
> It would be nice if the hot deployer knew when a module was last deployed.  That way, during startup, it could update deployments where the archive in the hot deployer directory had been updated while the server was down.  This would go into HotDeployer.getDeploymentTime (which currently is essentially a noop).
> It seems like the most expedient way to implement this would be to add a method to the config store to get the deployment time (given a URI).  David J suggests putting that method in a separate interface, something like TimedConfigStore or whatever.  It's not clear that it should live forever in the config store, but that seems like the best short-term plan.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira