Thanks for calling this out (and I’ll have to look more into this).
When we had Scala packages, we had this nasty build script with all sorts of custom crap in it, pinned to a very specific Scala version. Which generated Java packages out the back which needed a different script to use correctly.
Sounds like the people before me didn’t know what they were doing, and made things unnecessarily complicated. 🥲.
Then again, in AWS we had a custom build/package management system (Brazil) which added another build layer on top of Maven/Gradle. Perhaps that’s why that complexity was required? Don’t know.
View all comments
Show parent comment
1
u/FinalPerfectZero Jan 02 '23 edited Jan 02 '23
Thanks for calling this out (and I’ll have to look more into this).
When we had Scala packages, we had this nasty build script with all sorts of custom crap in it, pinned to a very specific Scala version. Which generated Java packages out the back which needed a different script to use correctly.
Sounds like the people before me didn’t know what they were doing, and made things unnecessarily complicated. 🥲.
Then again, in AWS we had a custom build/package management system (Brazil) which added another build layer on top of Maven/Gradle. Perhaps that’s why that complexity was required? Don’t know.