lahodaj commented on PR #8206: URL: https://github.com/apache/netbeans/pull/8206#issuecomment-2635909519
Sorry for belated answer. Traditionally, and in the strict API dependency sense, when adding a new API entry point, one needs to increment the module's version, so that other modules can require the new version, so that they can reliably use the new API. It is true that inside NetBeans itself, we didn't put too much effort into keeping the use sites up-to-date (i.e. module A is using API from module B, but is not explicitly requiring the version of module B where the API was introduced). So, the case is not very strong. I am not sure what's the advantage of not incrementing the spec version? We presumably still want meaningful `@since` tags, and at least an apichanges entry, what's the cost that would be saved by not incrementing the specification version? -- 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: notifications-unsubscr...@netbeans.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For additional commands, e-mail: notifications-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
