Yes, that's exactly what I was looking for. Thanks!
I've been thinking about it a little, and it seems that option 1 would be the simplest, except that--barring manually uploading the script to the maven repo--I think you'd need two gradle scripts or a script and a pom to do it properly. If you put the necessary elements in the script to upload it to the repo, then that would pollute anything that "inherited" from that script, right?
Is there any corollary in gradle to maven's "packaging=pom" that declares "this build script is the artifact that should be uploaded, which wouldn't be "inherited"? If you have to manually set it up in the script, then I think you're always stuck.
As I think about it more, I'm thinking the plugin approach might be the more desirable alternative.