Message:
The following issue has been closed.
Resolver: David Jencks
Date: Fri, 2 Jan 2004 7:28 PM
Based on the email discussion I am closing this issue.
The gist of the discussion is that it is not possible to reliably detemine file
modification times for non local "file" systems such as http, and that the
responsibility for determining if a file should be redeployed certainly does
not lie with the scanner, but with something that can interpret the contents of
the package. (consider redeploying based on timestamp change of a dd in an
unpacked archive).
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=GERONIMO-132
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-132
Summary: Adds deployments based on their modification time
Type: Improvement
Status: Closed
Priority: Minor
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Apache Geronimo
Components:
core
Assignee:
Reporter: Jacek Laskowski
Created: Sun, 21 Dec 2003 4:50 PM
Updated: Fri, 2 Jan 2004 7:28 PM
Description:
The coming patch modifies o.a.g.kernel.deployment.scanner.FileSystemScanner so
that it only adds a file or directory when its modification time equals to or
is greater then the time of the last scan
Added class' javadoc
NOTE: The class informs about its work's status. It may be appropriate to
reflect this in log4j.properties by rising its threshold to DEBUG or INFO.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
