On Sat, 3 Aug 2019 at 10:01, arsi <[email protected]> wrote: > > > Eric suggested elsewhere using the git hash as build number, which could > > work although might raise other issues. > > Hash is not a bad idea, but it would have to be just a hash of public > method signatures. > > An entire class Hash would cause a new implementation version at any > change in the body of the method, which would be counterproductive..
Note "git hash"! That would be a different implementation version for every source commit in the repository, even if no code changes in the module. It would mean we have a consistent implementation version across every build of a particular set of sources, rather than changing for every build of that source, nothing more. My question about using spec version loosens this slightly but still gives us unique implementation versions per release/update where required, while having the value in the sources themselves rather than dependent on an "external" source (git hash). > As I have already written, the easiest solution is to manually add the > implementation version to each ANB module and manually change them only > when changing the public method signatures. This is not what implementation version is for though - it's not about public API. Best wishes, Neil --------------------------------------------------------------------- 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
