[
http://jira.codehaus.org/browse/MNG-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121918
]
Joshua Pollak commented on MNG-3314:
------------------------------------
I can confirm this bug on maven versions 2.0.6, 2.0.7, and 2.0.8.
This is also a critical issue for corporate software teams with an internal
Maven repository which is not available to developers who are working offline
or at home where the internal repository is not available.
> 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
> Priority: Critical
>
> 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
