[ http://jira.codehaus.org/browse/MNG-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151525#action_151525 ]

bentmann edited comment on MNG-3314 at 10/21/08 1:24 PM:
------------------------------------------------------------------

IT for this has been updated to exhibit problem. The proposed patch (for the 2.0.x branch) simply skips the update checks for snapshots when Maven is in offline mode.

   was (Author: bentmann):
  IT for this has been updated to exhibit problem. The proposed patch simply skips the update checks for snapshots when Maven is in offline mode.

> offline build not running, when having SNAPSHOT dependencies
> ------------------------------------------------------------
>
>           Key: MNG-3314
>           URL: http://jira.codehaus.org/browse/MNG-3314
>         Project: Maven 2
>       Issue Type: Bug
>       Components: General
>   Affects Versions: 2.0.7
>        Reporter: Matthias Weßendorf
>        Assignee: John Casey
>        Priority: Critical
>         Fix For: 2.0.11
>
>      Attachments: maven-offline-snapshot-failure.log, maven-offline-snapshot-problem.tar, offline-snapshots.patch
>
>
> am having troubles with
> mvn ... -o
> (with maven 2.0.7)
> says not able to download (but, really, the file is in my local repo)
> The dependency is a -SNAPSHOT (for what's worth)
> Luckily, when traveling by train, I had maven 2.0.4 on my box as well.
> A change to use 2.0.4 works fine.
> So, is this an already know bug in 2.0.7 ?
> To my understanding it is a bug, since offline just shouldn't try to get a newer
> SNAPSHOT, perhaps I am wrong.
> I know that relying on SNAPSHOTs can be dangerous, but from -o I would expect
> just not checking for new stuff.
> and... for some reasons, sometimes,
> it just downloads a new SNAPSHOT.
> That is a pain, when you are "maintaining" the same snapshot on your
> box, but the build just goes ahead and actually downloads a version.

--
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