[
http://jira.codehaus.org/browse/MNG-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4758.
----------------------------------
Resolution: Duplicate
Assignee: Benjamin Bentmann
You can specify -U on the command line to force a remote trip.
> lastUpdated file created for releases
> -------------------------------------
>
> Key: MNG-4758
> URL: http://jira.codehaus.org/browse/MNG-4758
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Environment: JAVA_HOME=/usr/lib/jvm/java-6-sun
> Apache Maven 3.0-beta-1 (r935667; 2010-04-19 13:00:39-0400)
> Java version: 1.6.0_20
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.20/jre
> Default locale: en_CA, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-24-generic" arch: "i386" Family: "unix"
> Reporter: Mathieu Carbou
> Assignee: Benjamin Bentmann
> Priority: Blocker
>
> I have a project depending transitively on easymock 2.4
> (http://repo2.maven.org/maven2/org/easymock/easymock/2.4/)
> When connecting to download the dependency, my network connection failed (for
> 5-10 seconds) which made maven stop with a connection timeout.
> The issue is that a file has been created on my local repo for this release:
> easymock-2.4.jar.lastUpdated
> So when i re-executed the mvn package command, Maven keeps stopping with the
> same error (connection timeout), whereas it is now came back and working.
> I understand the purpose of the lastUpdated file: for snapshots they are more
> than required. But i really don't understand why the lastUpdated is also
> applied to releases. If a project is deployed and depends on a release
> version, I think Maven should keep trying to get this dependency in all
> available repository until it is found, because it's an illegal state to not
> find it.
> Also, by working in a large company, I really think this lastUpdated file on
> releases could really prevent or slow down Maven 3 adoption since this is
> quite an annoying think that will slow down people and increase the work load
> of the maven support team (at least because Maven will report false-problems
> that could be now solved).
> Is there an option or something that could be temporary put somewhere to get
> back to the same Maven 2 behavior ?
> Thanks a lot,
> Mathieu.
--
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
