Thanks for the links and words of encouragement, gents. I'll update the
blog entry accordingly.
I'm not a Maven committer (though i am an ASF member). I harang the
committers on rotating topics over the years, and at some point they'll
implement something similar to this if they want to. I love open source
where the 'upstream' team has a policy of patch consumption if they can't
state strong reasons for not doing so. And that's not Apache's policy.
Python3 proves to be a good prototyping tool. Maven's way is plugins, and
my creation/publish elapsed time would be 10x greater that way as I'd have
to learn it first. I think I'm faster with Java solutions than Python ones
generally, but not when I'm close to Bash. I could have done this in Bash,
but it'd have been six hours to make to this level of polish instead of the
three that it was.
Perfect world for me would be:
mvn -f buildThis.txt
Where buildThis.txt was:
compile:
foo, bar
test:
foo, bar, baz
That'd allow one invocation of Java, rather than two as I have it.
On the Maven sub-reddit, we've 40 new subscribers now as of this post :) I
love Reddit because of threading, in the same way I loved NNTP 20 years ago.
