GedMarc commented on pull request #26:
URL: https://github.com/apache/commons-fileupload/pull/26#issuecomment-623360761


   Ok. 
   
   @markt-asf Please review 
https://www.eclipse.org/lists/jakartaee-platform-dev/msg00029.html 
   Please review the outcome regarding the decision of 
   "Do we change the language level in Jakarta EE 9 to Java SE 11 or delay that 
to Jakarta EE 10?"
   Or rather -  Jakarta EE X. Don't appreciate your sny comments. Unfortunately 
the reality of X being on JDK 8 is currently where it is. There's quite a mail 
trail there, that's your starting point, can do the same work I did.  It's 
really not "up to debate" as much as "that was the decision made - so far"
   FUD. lol. Yes. 2026. That is the timeline.
   
   @rmannibucau  Yes I had to create the fork. Servlet 3 and 4 all work on the 
javax namespace, file upload is tightly coupled to these yes?
   
   @jochenw The bridge jar works perfectly, using a ```requires transitive``` 
in the module definition file - up to a point - but doesn't solve the separate 
classes issue. javax.inject.Inject and jakarta.inject.Inject unfortunately 
don't align, 
   There's also the problem of finalized or closed libraries - again i'm going 
to use the example of javax.inject which is a JDK 1.5 compiled and finalized 
JAR. 
   JDK 13 drops support for JDK1.5 classes entirely. Again I shaded this guy in.
   
   The decision is obviously all up to you, I've put in my concerns and my 2 
cents worth. 
   End of the day if the apache libraries don't come to the party we're just 
gonna repackage them until they work for modular development, so no sweat off 
anyone's back. 
   
   Guess I would just prefer the base to be into the new java world, instead of 
getting held back through a 6-month release cycle, for a product that goes 
through a 3/4/5 year release cycle.
   
   


----------------------------------------------------------------
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]


Reply via email to