> For the time being, project-c should use project-b from the local repository > because it's the latest 1.0-SNAPSHOT, right?
Sure. > Ok. Assume that now, the build server builds a new 1.0-SNAPSHOT of > project-b. From the documentation I've read on maven, project-c will now > resolve against the latest version; which is in the remote repository. Yes. But Maven will only see that changed project-b artifact if you tell it to look for it (via -U or --update-snapshots) or if the repository update policy is "always" or the specified timeout (via updatePolicy) has expired: http://maven.apache.org/ref/3.0.4/maven-settings/settings.html#class_snapshots > I have some ideas on how to solve this, none of which sound good to me, but > I first wanted to hear what anyone would suggest that I do, before I make > this post longer... If you simply limit the number of developers making changes to the same artifact simultaneously, this becomes a smaller issue and more manageable. If you cannot do that, then break your artifact into smaller pieces until you can. This is a problem no matter what build tool you are using and not specific to Maven. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
