You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/08/04 19:20:19 UTC

[jira] Created: (MAVEN-1414) 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

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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MAVEN-1414) 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

Posted by ji...@codehaus.org.
The following comment has been added to this issue:

     Author: Ian P. Springer
    Created: Wed, 4 Aug 2004 6:51 PM
       Body:
I tried w/ 1.1 HEAD, and it does work now. However, I think an additional line of (non-verbose-mode) output would be helpful. ie - the non-verbose-mode output is currently:
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.1-SNAPSHOT

Attempting to download addressing-SNAPSHOT.jar.
Plugin 'maven-deploy-plugin' in project 'Web Services Resource Framework' is not available
build:start:
...

but I'd like to see it look something like the following:
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.1-SNAPSHOT

Attempting to download addressing-SNAPSHOT.jar.
Local repo already contains latest version of addressing-SNAPSHOT.jar - no need to download.
Plugin 'maven-deploy-plugin' in project 'Web Services Resource Framework' is not available
build:start:
...

---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MAVEN-1414?page=comments#action_22759

---------------------------------------------------------------------
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: Closed
   Priority: Minor
 Resolution: FIXED

 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 6:51 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Closed: (MAVEN-1414) 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

Posted by ji...@codehaus.org.
Message:

   The following issue has been closed.

   Resolver: Brett Porter
       Date: Wed, 4 Aug 2004 4:28 PM

we already do all of this. There was a bug in 1.0 that if the charset was not US-ASCII it didn't work which has been fixed.
---------------------------------------------------------------------
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: Closed
   Priority: Minor
 Resolution: FIXED

 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 4:28 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org