On Wed, Sep 30, 2026, 14:38 Julian Reschke <[email protected]> wrote:
> > > Am 30.09.2026 um 20:01 schrieb Gary Gregory: > > On Wed, Sep 30, 2026 at 1:38 PM Julian Reschke <[email protected]> > wrote: > >> > >> Am 30.09.2026 um 17:47 schrieb Gary Gregory: > >>> Hi Julian, > >>> > >>> Commons in general follows sem ver: When the Commons Collection > >>> version changes from 4.5.0 to 4.6.0 it means a new public and/or > >>> protected API was added. > >>> > >>> Binary compatibility is paramount in Commons, so it is maintained as a > >>> matter of fact. > >>> > >>> HTH, > >>> Gary > >> > >> I get that; but that's per bundle, not per package, right? > > > > Per... Java package? What tool do you use to generate that info? > > > > Gary > That's the maven bundle plugin. > > It will compare with the latest release, and will fail the build if the > package version is not properly updated (and warn, when it as but > doesn't need to). > > Package versions can either be specified in the pom, or in the > package-info files. > > I can do some testing tomorrow (so to see what it reports for > commons-collections). > Hi. Unless the plug in figures out what's what by itself on a per package basis, this will be unmaintanable IMO. I don't see the point of this anyway since we publish a JAR file, not packages. Gary > > (and here's what ChatGPT - like it or note :-) says: > > https://chatgpt.com/s/t_6abd56a054a08191ac91857fcf336b30 > > Best regards, Julian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
