The only other avenue I can see is making the concept of (optionally) embedding a resource in published artifacts a first class concept. In that case, the jar publish goal could include advanced configuration options to maybe accept a template and produce a resource using that template along with a way to name the path the resource gets added to the jar with. That might not be totally unreasonable given the precedent, for example, of maven metadata files in jars.