Never mind.. I think I see what happened.. apparently I messed up a version
of a child dependency which became out of sync with everything else.. this
apparently caused the release plugin to go completely haywire. Telling it I
didn't want to resolve the dependency made the build quit but with an e
I've been struggling with the maven2 release plugin but have managed to get
the majority of my problems except for one. For some reason when I do a
release on a subproject that I've previously managed to successfully
released before, the maven2 release plugin will keep repeatedly asking me
for the
