Chat Logs

  1. dob1_I don't know who are gradle devs but really every version update is a nightmare... imho it is like tr*sh, it has to be a tool to help developers not to complicated their life!!! and even with AI it is difficult to upgrade a build.grdle
  2. dob1_and you cannot skip a versione because if you update your java version if you have to update gradle too
  3. dob1_I don't understand what they do moving something somewhere else with a different name and with a different context. What they will archive with modifications like this one ?
  4. dob1_(sorry for the rant)
  5. dreamrealdob1_: this is why I don't use gradle any more in my own projects
  6. dreamrealthe devs have a policy of progress, period, so if they think something's good, there it is, compatibility be damned, that's what version locking is for
  7. dreamrealgradlew is your friend
  8. dreamrealand all this is known, none of it's hidden or private, it's public knowledge
  9. dreamrealgradle's really good until it's not, welcome to adulthood, I guess, I dunno
  10. ZapekI thought they improved lately. haven't had any big breaks for years
  11. dob1_for me it seems like some gradle devs wakeup in the morning and says "what if we remove this or add this one"
  12. dob1_maybe there are some secret plans that you have to read all the manual every time to understand them, but it doesn't seems that they changes will improve the tool in a very useful way... they are just changes
  13. dreamrealI think they're conceptual changes, I mean, they HAVE a sort of vision and they're moving toward it, but it's not a written spec to comply with, it's "let's make this the best tool we can think of"
  14. dreamrealand they keep thinking of slightly different things
  15. dob1_it's like an "abuse" of semantic versioning
  16. ParaTheir vision's biggest issue is that they're vision is to be all the things, while normally vision should focus onto being one very specific thing.
  17. dreamrealPara: ++
  18. nevetPara now has karma of 3.
  19. dreamrealdob1_: Well, semantic versioning IS only a suggestion... and if they obeyed it, we'd be on gradle 58 now! IS THAT WHAT YOU WANT?!?!?!?!
  20. dob1_no :)
  21. dob1_you said there is a vision well I don't know because I think that people who started and worked on the projectd changed in the years, so they are supporting a vision that has change though the years
  22. dreamrealTeh current developers' vision is not the same as the originators', necessarily
  23. dreamrealthat's how project handovers work
  24. dob1_for java it is like one tool that you can use, even if it is very popular, but for android I know it is mandatory. And they are not affected by all these changes every version?
  25. dreamrealgradlew is your friend, I think I mentioned that already, it's almost like I meant it
  26. dob1_I use the wrapper
  27. dreamrealit is your friend and defender
  28. dreamrealavoid it at your peril
  29. dob1_it's not, if you want to upgrade your java version you must update gradle too
  30. dreamrealfoojay is no help?
  31. dob1_I didn't know this site
  32. dreamrealit's a gradle plugin
  33. dob1_I read about it and imhook the main problem is still there, when you run a gradle task with a new gradle/java version it gives you a lot of errors.
  34. dreamrealbummer. I leave our gradle build to someone else, and we don't build for android
  35. dob1_me too, I don't build for android. It was a consideration
  36. dreamrealI'm just glad I can pawn it off: we have an incredible build system, it's truly awesome, I'd never be able to build it the way we do
  37. hassoon'evening
  38. lava~pastebin
  39. javabotPlease paste your code and any errors online. For runnable classes, try https://ideone.com/ . For general code and errors, use https://gist.github.com or https://dpaste.org/
  40. nevetDiscover gists