You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/11/15 06:44:27 UTC
[jira] Created: (GERONIMO-1174) Hot deployer should know when a file was last deployed
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
Components: deployment
Versions: 1.0-M5
Reporter: Aaron Mulder
Fix For: 1.0
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
[jira] Resolved: (GERONIMO-1174) Hot deployer should know when a
file was last deployed
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1174?page=all ]
Aaron Mulder resolved GERONIMO-1174:
------------------------------------
Resolution: Fixed
> 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
[jira] Closed: (GERONIMO-1174) Hot deployer should know when a file
was last deployed
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1174?page=all ]
Vamsavardhana Reddy closed GERONIMO-1174.
-----------------------------------------
> Hot deployer should know when a file was last deployed
> ------------------------------------------------------
>
> Key: GERONIMO-1174
> URL: http://issues.apache.org/jira/browse/GERONIMO-1174
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Hot Deploy Dir
> Affects Versions: 1.0-M5
> Reporter: Aaron Mulder
> Assigned To: 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
[jira] Updated: (GERONIMO-1174) Hot deployer should know when a file was last deployed
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1174?page=all ]
Dain Sundstrom updated GERONIMO-1174:
-------------------------------------
Fix Version: 1.1
(was: 1.0)
> 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
> Components: deployment
> Versions: 1.0-M5
> Reporter: Aaron Mulder
> 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
[jira] Updated: (GERONIMO-1174) Hot deployer should know when a
file was last deployed
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1174?page=all ]
Aaron Mulder updated GERONIMO-1174:
-----------------------------------
Component: Hot Deploy Dir
(was: deployment)
> 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
> Components: Hot Deploy Dir
> Versions: 1.0-M5
> Reporter: Aaron Mulder
> 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
[jira] Updated: (GERONIMO-1174) Hot deployer should know when a
file was last deployed
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ 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