matthiasblaesing commented on issue #3878: URL: https://github.com/apache/netbeans/issues/3878#issuecomment-3307434314
The general idea is, that if a module exposes an API the change is to be documented in `apichanges.xml`. However the `dlight.nativeexecution` has no public API (the API is friend only), so rules are relaxed. Additions to the API of a module in general require a spec version bump (minor version), but minors are bumped on each release, so changing the version is not strictly necessary. Users of "dev" versions will need to use a consistent set of modules built from the same source though. The dependent module needs to raise the dependency it declares to the current spec version of the dependency, so that it is ensured, that the added functionality is present. Inspiration for the functionality might be taken from the SQL history, which covers a similar usecase: <img width="722" height="427" alt="Image" src="https://github.com/user-attachments/assets/a8406fa7-32db-41be-b071-beb3faeeb40f"; /> -- 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
