matthiasblaesing commented on PR #6257: URL: https://github.com/apache/netbeans/pull/6257#issuecomment-1650550558
> I'm still not convinced this is the right approach as it keeps the need to touch the code on every new EJB release. Maybe. If the next EJB release is breaking (aka 5.X), then yes, but then you need to check that code anyway to see if it affected by the breakage. If it is 4.1 (a true superset), then https://github.com/apache/netbeans/blob/b79fd30b2e76ed070789745cabcf14bf5cf1e330/enterprise/j2ee.common/src/org/netbeans/modules/j2ee/common/J2eeProjectCapabilities.java#L158-L162 and https://github.com/apache/netbeans/blob/b79fd30b2e76ed070789745cabcf14bf5cf1e330/enterprise/j2ee.common/src/org/netbeans/modules/j2ee/common/J2eeProjectCapabilities.java#L171-L175 can centrally be updated to cover the next JakartaEE version and you are done. API breaks always mean, that you have to check code, especially if the compiler can't really help you to diagnose problems. Nothing special there. The classes I marked as `@todo` show IMHO that we are currently seeing only the tip of the iceberg and there is more breakage lingering. -- 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
