rmannibucau commented on pull request #26: URL: https://github.com/apache/commons-fileupload/pull/26#issuecomment-623354193
@jochenw all "real" (as "for prod") attemps use bytecode rewriting like the tomcat jakarta migration tool and alternatives. Bridges assumes you have both all the time so only fits very few libraries which always prefer to abstract their on usage and therefore have a spi and 2 modules supporting javax and jakarta. Would mean commons-upload gets 2 new modules or (to not break backward compatibility for most users) keep commons-upload as an aggregator, adds javax and jakarta integrations and adds a parent and shared modules (so 5 modules at least). Issue being jakarta compatible now means that the current version will stay mainstream for at least 2 years (jakartaee 9 was planned for june this year - I suspect it can be late but this is just a blind guess, if you add impl time + time to be used it brings us in some years so you end up with a master not consummable yet. Last is that tomcat uses that and will support javax for years so I guess javax must stay for now and jakarta be enabled only and this should be reconsidered when data proves jakarta is used I guess. ---------------------------------------------------------------- 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]
