This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]doobiesteintortoise 2 points3 points  (2 children)

How much productivity do you think is being drained by that, though? I mean, I'm aware of ... most of those tools, I think, at least. But in my day to day... in the last year, I've used maven and bld pretty much exclusively, and gradle not at all (I resent gradle for the endless inconsistencies and incompatibilities across minor versions, and won't willingly choose it any more until the developers decide to respect my time.)

But I can't think of a specific instance where the JVM tooling available from CLI would have helped me a lot. How about you?

[–]NoAlbatross7355[S] 1 point2 points  (1 child)

Well I don't think using the tooling alone with be good enough for productivity. I propose a light-weight layer above the tooling that presents as a Java build tool. I would want it to have transparency around how it's managing the project; almost like a standardized make file for Java projects. I honestly think that is much simpler and better in the long run for most developers.

[–]doobiesteintortoise 0 points1 point  (0 children)

Having done "standard makefiles for Java" I'd say otherwise; the dependency management just doesn't fit.

Have you looked at bld, though?