When you refer to central, you mean your own centralised repository, not Maven central, correct? You shouldn't be receiving updated artifacts from there (except for new plugins, which can be avoided by locking down versions).
To control the regularity of updates from other repositories, you can set the <updatePolicy> for the given type within the repository element. What it looks like you need to do is to set up a repository manager that houses the integration lanes and manage what updates you want to get in there, then your environment can direct all repository requests to the single repository manager. - Brett 2008/8/8 vicki <[EMAIL PROTECTED]>: > > Hi, > each developer in our group has his/her own integration lane. The code is > compiled with the different db schema variables for each developer so, > effectively, the artifacts produced by each developer's profile are > different. But sometimes when the integration task deploys the code in my > lane, it updates the artifacts in my local repository with the artifacts > from the central repository, in case if central repo artifacts have a more > recent compilation timestamp. This is screwing up my schema references. Is > there a way to force maven NOT to update local repository, or to exclude the > central (or any other) repository from the repositories specified in my > integration profile? > Thanks! > Vicki > -- > View this message in context: > http://www.nabble.com/How-to-exclude-some-repositories-from-a-child-pom--tp18877415p18877415.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Brett Porter Blog: http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
