[ http://jira.codehaus.org/browse/MNG-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236214#action_236214 ]
Scott Marlow commented on MNG-3006: ----------------------------------- I'm using a newer maven but seeing a similar issue (I'll create a new jira if its thought to be different). I'm using "Apache Maven 3.0-beta-1 (r935667; 2010-04-19 13:00:39-0400)" and occasionally get intermittent "connection refused" errors. The problem is that this error is cached (as this jira reports for other problems) in the local Maven repo. Deleting the cached entry, helps get the connection attempt to be retried. Maybe Maven should automatically retry the connection attempt initially (waiting an increasing amount of time between attempts before finally giving up). Would that help with the original issue reported by this jira? By the way, my cached entry (dtdparser121-1.2.1.pom.lastUpdated) contains: #Last modified on: Thu Sep 23 10:20:54 EDT 2010 #Thu Sep 23 10:20:54 EDT 2010 https\://repository.jboss.org/nexus/content/groups/developer/.error=Error transferring file\: Connection refused 83570450015= https\://repository.jboss.org/nexus/content/groups/developer/=1285251654064 > Maven does not always download artifacts from specified repos > ------------------------------------------------------------- > > Key: MNG-3006 > URL: http://jira.codehaus.org/browse/MNG-3006 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories > Affects Versions: 2.0.6 > Environment: Windows XP SP2 > Reporter: David Hoffer > Fix For: Issues to be reviewed for 3.x > > Attachments: settings.xml > > > Performing maven2 builds does not always downloaded requested artifacts from > specified repos before complaining that the required artifact is not > available and giving up. However if I delete my local repo then it always > works. > Here is the failure log: > [12:42:04]: Couldn't find a version in [1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, > 1.7, 1.8, 1.9, 1.10, 1.9-SNAPSHOT, 1.11-SNAPSHOT] to match range [1.11,) > [12:42:04]: com.xrite.retail:retail-commons-classic:jar:null > [12:42:04]: > [12:42:04]: from the specified remote repositories: > [12:42:04]: central (http://xrbuild3:8081/artifactory/repo), > [12:42:04]: snapshots (http://xrbuild3:8082/artifactory/repo) > An HTTP port monitor shows that maven refuses to contact the servers until I > delete my local repo. Maven should always check the remote server before > giving up. > I will attach my settings.xml. -- 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