BTW, my particular issue has already been resolved by Wendy pointing out
that according to the logging messages there seemed to be something
configured to deploy a jar in addition to the war that I was expecting to be
deployed. The jar is what was being deployed to the releases repo.
The distributionManagement and respository configurations were all correct.
Someone had hooked up an additional "deploy-file" to attempt to deploy the
classes used in the war and was improperly directly using
${project.distributionManagement.repository.url}
for it's URL.
This was changed to use the attachClasses option of the war plugin so that a
jar is also deployed with the 'classes' classifier.
