What good is checkModificationExcludeList for release:prepare?

I'm using the release plugin for tagging and branching on CVS projects. Certain user-specific property files should not be taggeg nor branched, so I defined checkModificationExcludeList for the release plugin. This passes the first modification check well, but when it comes to tagging by scm

No reattempt to resolve broken released artifacts

Hello, we shortly switched our company's infrastructure to maven and are now experiencing a strange behaviour of dependency resolution. Say my.project:1.0.0 requires my.cool.component:jar:3.7.0 and I try to build my.project:1.0.0 before the dependency was deployed to my central repository, my

Dependency resolution problem

(2.1.0) P - B (1.3.0) should cause a build failure, a setup like P - A (1.1.0) - B (1.5.0) P - B (1.3.0) should not, but we have to guarantee, that B (1.5.0) is resolved, not B (1.3.0), which is not the standard maven dependency resolution. Has anyone an idea how to solve this? Regards Frank