I'm in Indonesia, and reddit is censored here :-) even though it's as prevalent as youtube in technical value second only to SO.
|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. amen. i really, really hate build tool dualism. maven's success in eradicating jelly, and all conditionals and branching options was the impetus that made ORM's viable and transferable project nkowledge probably for the first time. jdk nio Files.* is better than what was on hand when maven plugins were defined. I don't know how you solved build resolution but .. the maven plugin boilerplate is as few as two annotations and reading some visitor javadocs. for god sakes why can't gradle just emulate a maven build-daemon instead of deprecating the object model at every chance? Reactor architecture is ancient, and last i checked, the maven plugin list is a ghost town barely active enough to review and retire some of the first codehaus (your old stomping ground) ported plugins python is great, while you're on the machine you wrote it on. once you import a package, it's a less reliable tool than a maven plugin, at a cheap cost to prototype. polyglot-maven <https://github.com/takari/polyglot-maven> might be what's next, enabling type-optional languages which incidentally brings inline imperative syntaxes for free. is it time to look the other way on imperative languages in maven project object models? On Wed, Oct 23, 2019 at 12:26 AM Paul Hammant <p...@hammant.org> wrote: > 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. >
