Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
what build system
intern manually running tasks by hand
some gigantic proprietary system that only runs on windows
random link to github project with no commit in 3 years
goku
View Results
 
  • Post
  • Reply
dads friend steve
Dec 24, 2004

alright so if not maven what am I supposed to use to build my trash java apps?

Adbot
ADBOT LOVES YOU

dads friend steve
Dec 24, 2004

oh my god no

dads friend steve
Dec 24, 2004

it sounds like ANT where I need to understand each projects bespoke build process instead of relying on the tool enforcing a consistent system that works in all realistic cases

dads friend steve
Dec 24, 2004

I guess I should add that I view it as a feature that maven forces you to conform to it and enforces a fairly high barrier to entry (building your own plugin) to diverge

dads friend steve
Dec 24, 2004

Gazpacho posted:

gradle provides modules that can be configured similar to maven using far more efficient and readable syntax (lol @ hand-edited xml)

however it is magical thinking to suppose that these pre-existing modules will always cover the emergent needs of any organization and for those cases gradle lets you go procedural as needed, reusing parts of those modules at the level where they are indeed reusable

maven's architecture is that any emergent need has to be captured immediately as a plugin, before you can proceed at all. you don't get to express it procedurally at first so that you can feel out the requirements and what the configuration points are. this pushes you to create "reusable" plugins that are not in fact reusable and should be done over, but we know that necessary do-overs have a way of not ever happening

(though in observed practice people will just hack in an antrun goal rather than create a plugin, while crossing their fingers that it doesn't conflict with maven's "opinions" about goal sequencing, because bro there's a friggin deadline)

I’m gonna ignore the hand wringing over xml because honestly who cares

during my entire time developing java I have never had a case where we had emergent build system needs that we needed to iterate on because mavens extremely generic clean -> compile -> test -> package -> deploy flow covered it. the build system should be a very boring implementation detail, I want to spend next to no time thinking about it.

the only time I’ve really seen people want to break out of the maven way of doing things is when they want to produce more than 1 artifact per project, and maven forcing them to use multiple projects instead usually results in a better design

dads friend steve
Dec 24, 2004

Progressive JPEG posted:

the core of jenkins sends RPCs by serializing a java object containing the code to be executed, then sending it to the worker node

the worker node then deserializes and executes the object

i call it RPC by RCE

this is also why java versions must exactly align across all the jenkins machines

lmao

dads friend steve
Dec 24, 2004

Gazpacho posted:

even if i had it it wouldn't be mine to post, and anyway we both know that your response would be "why are you doing the dumb things" while ignoring the answer I have always given, that the management mandated the use of maven while also imposing requirements (esp. variant builds) that conflict with maven's "opinions"

that is lovely, and also not maven’s fault

dads friend steve
Dec 24, 2004

the purpose of a build system is to be better than rolling your own Frankenstein build process that’s probably going to be a bunch of shell scripts janitoring the file system, calling the compiler, etc. Some build systems, like maven, make the design decision to enforce a standard project layout and build pipeline, which is a perfectly valid choice

dads friend steve
Dec 24, 2004

the closer your build tools are to imperative scripting, the further they are from righteousness

Adbot
ADBOT LOVES YOU

dads friend steve
Dec 24, 2004

I have no good answer to the question above, but I do have a question of my own: how is it that you have PRs all to the same repo and at such a frequency that you have that problem to begin with? Like how is that happening so often you need automation?

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply