Just wondering... anyone else think having a script automatically kill gradle if it runs for more than X amount of minutes would be a great sanity saver?

"Jesus Fucking Zombie Christ I only added ONE FUCKING TEXTVIEW IN A SIMPLE GODDAMNED LINEAR LAYOUT YOU WORTHLESS MOTHERFUCKING PIECE OF SHIT AND GRADLE IS STILL RUNNING AFTER FIVE MOTHERFUCKING MINUTES?!?!?!?!?!!?!?!?!?!"

Gradle builds are fucking annoying.

tl:dr
i fucking hate that professor for whom i have to work on laboratory project right now.

reason#1
the project is using a stack full with java. JavaScript. react and some weird facebook api of which i have no clue about. not to mention the server side of this application which uses tomcat (ok its java after all) and sql.

well that wouldn't be not so bad if...

reason#2
we wouldn't have to fucking debug his mistakes he put into the fucking prepared code AND his fucking useless instructions how to set up the project for eclipse the first time. not to mention his fucking requirements which make no sense

oh yeah im a student. i can always go and ask him for help if i need any...

reason#3
i have another 70% mandatory course at the same time and that fucker refuses to upload hos sheets in moodle and answer even one fucking question via mail. not to mention no support if I am there unless i have eclipse setup. even through the projects should be build using gradle...

reason#4
oh. and have i mentioned that this course is only about design patterns? uts not like we could see several of them in a java only application. no we literally have to learn java itself. gradle. nodejs JavaScript Extended for react which i have no clue about at the moment... and yes i especially mentioned gradle and nodejs beccause we have to set shit up and not only use a script.

reason#5
and all that wont even give us a grade. no ita simply a pass or fail part of the module which the course is part of.

have i also mentioned that the whole shit should be done in 20 hours according to the schedule

Heck yeah,
So an old Ionic 3 project wont work on the newest CLI.
I check around for the error, update some dependencies, sure enough it starts working again, all is great or so I thought.

Later something weird starts happening, upon pushing a new view on the navCtrl, the navParams are null on the next view.
I later find out that navCtrl is becoming navParams just on the first bit of the view loading, so I do a dirty fix just to keep working on the functionality from my browser, I know very well this will cause problems later on, this is just so I can keep working on functionality.

I finish all of the functionality and I'm ready to compile for android, I run my script, the dirty fix comes to bite my butt now.
I remove the dirty fix hoping for it to work just well on the apk.
Now gradle doesn't find ddmlib.jar, some 15 minutes of troubleshooting do nothing.

Fuck it, I'll just create a new project from the CLI and drag all the code there so that navParams work as expected.

Sorry Ionic, but the world is not our oyster when subtle changes in dependencies produce such unexpected behaviour, with some fucking view parameters!.

I'm looking forward to get done with all the current projects to jump back to native.

Just had a complete nerd-gasm as I finally got my gradle plugin script to perform multi-module releases correctly and efficiently

Soooo I am an apprentice who just started his third year. Everybody in my team (3 ppl) left for better jobs.
I am now basically front and backend lead, teaching four new employees our restapi, web and javafx frontend.
At the same time I fix errors happening in production and develop new features.
I guess there are many great rants to come, so stay tuned :D
Going to write about things like tests that got disabled months ago after migrating to gradle, no documentation, finding out how to set up new development workstations with an outdated script missing important steps, management, print debugging in production and much more :)
Oh and it is not that bad, I learned more in the last month than in the two years before. (not saying my team was bad)

So, I have a pretty decent understanding of big complete languages like Java, I build android applications following several design patterns, solid principles, building big stuff with databases and servers and libraries interconnected with gradle, tracking everything with git, using tdd and functional programming capabilities blablabla ... And I still have trouble making sense of a FREAKING STUPID SHELL SCRIPT I MEAN WHO CAME UP WITH THAT SINTAX I HATE IT SO MUCH OMG I CAN'T EVEN
But for real everytime I need to read a '.sh' I literally wanna throw my computer away and die. Am I alone?

Run ./configure and gmake directly, it works.
Run a gradle script with exec tasks that runs the same commands, and the binary doesn’t run complaining about a library.

Fuck you AIX.

I haven’t fully root-caused it yet. I’m assuming something is fucking up during configure.