OndroMih commented on PR #6212: URL: https://github.com/apache/netbeans/pull/6212#issuecomment-1666871030
Hi, my gut feeling is as long as the component version is supported by the latest Jakarta EE, it’s OK to assume that it will continue to be supported for future versions. In the worst case, older versions of Netbeans will generate code that will need to be fixed by the user and newer versions of NB will fix the behavior to return false for newer Jakarta EE versions that break the API. IMHO it’s better than not being able to generate any code. E.g. isEjb40Supported() would be OK as in this PR. But for older versions, e.g. is Ejb31Supported, they should only return true for Jakarta EE versions that don’t break the API. In this case, Jakarta EE 9 is no linger compatible with EJB 3.1, so isEjb31Supported() would be true only for JavaEE 6-8 and Jakarta EE 8. This way, we’d only need to fix Netbeans in case there’s another breaking change in Jakarta EE. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
