Something is wrong with the current snapshot update policy: I have a several projects going on concurrently; the first is intended to be a common components type project for the others, all are in concurrent development. The upstream project SNAPSHOT jars are *never* getting downloaded. I think this is because the upstream parent pom has an older version, so when maven checks for modifications it also checks the upstream parent pom, sees that it is not updated yet, and skips downloading the upstream child even though it is newer. This behaviour is dead wrong especially for an update policy of "always". This is also breaking development within the downstream project as the project consists of 6 sub projects, and with one team working on the core subproject and another on the web subproject, this gets frustrating when we have to spend time trying to figure out why the projects are not compiling.
Short of periodically deleting the artifacts from the local maven repo is there anything that can be done?
