> This would seem to present a problem if you are working on a project > simultaneously with other developers who may be deploying to the internal > remote repository. Suppose you add a new method to a common library and then > change another project to use that method. While you're testing, another > developer checks in a different change to the common library and deploys a > new snapshot. M2 sees that as the latest snapshot and now you're working > with a version of the library that does not have your new method. This would > force you to re-install your version of the common library in order to keep > compiling. > > Does that all sound correct?
If this is correct, then you need to pull out any snapshot repositories out of your normal build process. Where is your snapshot internal repository declared, in settings.xml? If settings.xml make sure it is in an inactive profile, then you can use -P to turn that profile on when you want to include snapshots. If it's in pom.xml, I am not sure what you can do. I'm not an expert enough to answer. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
