matthiasblaesing commented on PR #6212: URL: https://github.com/apache/netbeans/pull/6212#issuecomment-1648431780
I think the versioning is sane: EJB 4 is a breaking change and thus deserves to to be treated differently. From an IDE perspective, you have to check all generated code as both XML, as the package namespaces were changed. What more should change, that warrents calling it an incompatible change? I accept, that for humans EJB 4 is more or less EJB 3, but from an technical perspective they are different. When I ask the question "Is EJB 3.2 supported?" and I get a "yeah sure", then I would generate code relying on the `javax.*` namespace and IMHO I would be rightfully expect it to work. Yet an EJB 4 server can validly reject that code as it does not need to implement it, as it only claims to support EJB 4. -- 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
