GedMarc edited a comment on pull request #26: URL: https://github.com/apache/commons-fileupload/pull/26#issuecomment-623136538
The core java support for security, threading and many others, is.. And this is in jakarta space, which does make it non-compliant. Do you use bouncy castle? do you use threading? do you use CDI which performs illegal injections?. Are there classes and resources in the root path that will be completely inaccessible JDK 12 and up? There is a reason Jakarta is in JDK 8 for the next 2 releases in a 3/4/5 year cycle. Modular, strictly encapsulated, MicroService development - and CDI/EE are competing strategies. They do not support each other, they are two completely different ways/styles of development. Going the one, you negate the other. The reason Java EE was thrown was for no other reason except "The technology has been superseded" Going JDK 9 and up without going modular gives you performance degradation, because the Class Loader is "backwards compatible". That means it will get deprecated eventually, and now with oracle that means it will get removed. Or at least we truly hope so. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
