You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/08/25 07:25:03 UTC

[jira] Closed: (MAVEN-1672) about warning last-modified not specified an 0k donwloaded

     [ http://jira.codehaus.org/browse/MAVEN-1672?page=all ]
     
Brett Porter closed MAVEN-1672:
-------------------------------

     Assign To: Brett Porter
    Resolution: Duplicate

thanks for the additional info!

> about warning last-modified not specified an 0k donwloaded
> ----------------------------------------------------------
>
>          Key: MAVEN-1672
>          URL: http://jira.codehaus.org/browse/MAVEN-1672
>      Project: Maven
>         Type: Bug
>     Reporter: Stephan Hartmann
>     Assignee: Brett Porter

>
>
> This is maybe not a maven bug, but i want to tell the solution for a problem that seems to occur from time to time but noone knows a solution.
> Sometimes when using dependencies to snapshots of own packages there appear warnings like:
> warning: last-modified not specified
> 0K downloaded
> sometimes more than once. Maven prints out a bunch of unzip errors and compile errors.
> In my case, i had a snapshot of a own packaged deployed to a local repository. In another project i had a dependency to this package. In my maven.repo.remote i had specified my local repository and then ibiblio.
> I got this damn warning two times and the downloaded snapshot in my cache seemed to be empty.
> The problem was that maven first looked in my local repo and found the snapshot and downloaded it. But it also looked at ibiblio. But ibiblio didn't have the package (it's a own development). But instead of reporting a 404 HTTP error ibiblio reports a 200 with a normal HTML page. So maven overwrote the package in my cache with this HTML page.
> This may also happen, when you have no local repo and only ibiblio and install your dependency packages with ejb:install-snapshot.
> maven will always look on ibiblio for newer snapshots.
> The solution is currently to switch to another mirror (public.planetmirror.com reports 404 errors).
> I think it is at least worth to mention this in the FAQ and switch from ibiblio to another repo server as default.
> Regards,
> Beffe

-- 
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
-
For more information on JIRA, 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