maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tamás Cservenák (JIRA) <j...@codehaus.org>
Subject [jira] Created: (MNG-4616) Consider a settings option for setting updatePolicy "always" globally for all snapshot-enabled repositories
Date Thu, 01 Apr 2010 11:17:22 GMT
Consider a settings option for setting updatePolicy "always" globally for all snapshot-enabled
repositories
-----------------------------------------------------------------------------------------------------------

                 Key: MNG-4616
                 URL: http://jira.codehaus.org/browse/MNG-4616
             Project: Maven 2 & 3
          Issue Type: Improvement
          Components: Settings
            Reporter: Tamás Cservenák


Consider a settings option for setting updatePolicy "never" globally for all repositories.
This should be applied to snapshot-enabled repositories.

Consider following (I would say most common) scenario:

UserA and UserB works on same subnet. They share same SCM server where they push changes.
Their CI server builds regularly by pulling SCM changes. They both use a MRM proxy on same
subnet that acts as a proxy and hosts their CI deployed artifacts (snapshots and releases).

If UserA builds in the morning, he's Maven will check for new snapshots, and (by default)
will never check again for them.

Later, UserB makes a change, that will (after SCM push and CI build) get deployed to their
MRM as a snapshot.

UserA will not get the change unless specifies "-U". This may sometime lead to problems, and
have UserA and UserB "fall out of sync".

In this case, the MRM in between users and the "rest of the world" already _handles_ caching
and aging, hence the Maven (as client side) aging just makes bad interference with it, and
_may_ be a source of problems.

It would be cool, to just set up maven "as best practice" (pointing it to some aggregated
repo), and just turn of the "aging" (set updatePolicy to "always") and forget about forgotten
CLI commands like "-U" is.

Or is there some consideration I forgot from this story?

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

       

Mime
View raw message