I really hope there is a quick patch for this because I don't have a good workaround other then not deploy files. I think I've discovered a bug where if a Maven project has no PRIMARY artifact, TeamCity doesn't recognize this and thinks it has one anyway. See:
This project has NO primary artifact. It's just one with a classifier that gets set to the current branch name.
This is causing the Artifactory plug-in to go nuts:
It can't find a file. And based on the stracktrace it's because TeamCity is pointing the plug-in to a non-existent file.