Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MAVEN-1414 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-1414 Summary: when SNAPSHOT jars are pulled, store current timestamp in local repo, then only download in future when HTTP last-modified header time is later than stored timestamp Type: Improvement Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Versions: 1.0 Assignee: Reporter: Ian P. Springer Created: Wed, 4 Aug 2004 1:18 PM Updated: Wed, 4 Aug 2004 1:18 PM Environment: n/a Description: SNAPSHOT jars get downloaded every time Maven is run, even if they have not changed on the remote repo. My suggestion is to introduce a timestamp comparison between the SNAPSHOT jars in the local and remote repos, in order to determine if it is necessary to download the SNAPSHOT jar from the remote repo. This could be done via an HTTP HEAD request for the remote SNAPSHOT jar, and then inspecting the HTTP Last-Modified header. To be even more robust, the files' sizes could also be compared by looking at the HTTP Content-Length header. --------------------------------------------------------------------- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
