Run this from a command line in you basedir and post the result:
Most likely some other dependency is also referencing the same dependency and Maven is choosing the non-snapshot version over the snapshot version.
The other thing you can do is run mvn with the -v option, redirect the output to a file and examine it looking for reference to that dependency to see how Maven is going about choosing a version to use.
Thank you Peter Johnson. I tried to attach the output of "mvn dependency:tree", but the forum won't allow it (.txt or .zip). I'm reluctant to put project info from my (newly joined) company online where it can be easily indexed by search engines. I didn't realize this was an issue here and might make it difficult for me to use JavaRanch for more project-specific stuff, but the info you gave me will help me track down the issue I hope. I will rebuild with -v also and see what comes from that when I build next.
I understand the necessity for keeping proprietary company information confidential. You can usually work around that in two ways:
a) come up with a small example that exhibits the same problem but doesn't include any proprietary information
b) obfuscate anything that could be proprietary (such as package names and JAR files name), but make sure that your renaming is consistent
But even with those restrictions, you can often get help here - we can give you hints on what to try and look at (such as the -v suggestion). Often that can be helpful.