3 ms·
On the other hand, if porting our app to Java9+Jigsaw requires us to wait a year (because breakage with maven), costs like half a year to a year (I know our cod
by tetha 10y ago
On the other hand, if porting our app to Java9+Jigsaw requires us to wait a year (because breakage with maven), costs like half a year to a year (I know our codebase), while upgrading our application servers (because classloading) and possibly re-doing a lot of the build process at the same time... I'll have to support Java8 for just about forever.
That upgrade wouldn't happen, or it would be really nasty. I'll rather tolerate a standard library with a lot of bollocks in there and provide security around it.
- jfoutz 10y agoaww shucks. Yeah, i understand. Backwards compatibility is hard, and java has been pretty good (there have, of course, been a few rough spots). I'm surprised there's no answer at all for maven. I'd assumed there was some sort of import * to just grab everything, like we're all doing right now. Going and adding a single line to a few hundred build.xmls doesn't sound excessive. shrug
- melling 10y agoPeople have been waiting a decade now? I remember listening about Jigsaw on the Java Posse back in 2009: http://javaposse.com/java_posse_259_jigsaw_and_jsr_294_interview http://javaposse.com/java_posse_259_jigsaw_and_jsr_294_inter... https://jcp.org/en/jsr/detail?id=294 https://jcp.org/en/jsr/detail?id=294
- tetha 10y agoI didn't mean wait for Jigsaw. I meant: Assume jigsaw breaks maven, i.e. it's not compatible and there's no easy ugly workaround without runtime errors. That'd mean, my place - and pretty much every place - has to wait at least a year or more, until all dependencies are ported to jigsaw. If all dependencies get ported. This sounds way too similar to the whole Python2/Python3 mess to me to be a good idea.