Hello Ben,
We could probably release a new version if this can help. @Lennart? As you've been the de facto maintainer here seeing the last commits, WDYT?
BUT, anyway, the right way to handle that in your organization is to have a maven repository manager. If you don't have one, really, you're in trouble. Go set up one, and go back :-).
Or are gonna be some day.
In the current case, to answer your use case, you would just package a local version of jaxb-maven-plugin and push it to a dedicated "3rd-party" repo. Then your colleagues would immediately be able to use it, since obviously everybody in the company uses your Maven Repo Manager as a mirror and deployment target (Search for Nexus, or Artifactory, those days).
Cheers