Nope, that is in fact "bending" the things, just to apply your own interpretation.
Maven: - does document what can be used or not - does uses well-known convention of package names (ie impl or internal) - does place Javadoc onto classes explaining what they are (and should they or should they not be used) - tries its best to provide help to users (ML or issues) Everything beyond this above, for me, is classified into the same box as "don't dry kittens in the microwave oven..." advice. T On Wed, 9 Sept 2026 at 13:47, Elliotte Rusty Harold <[email protected]> wrote: > > On Tue, Sep 8, 2026 at 6:17 AM Tamás Cservenák <[email protected]> wrote: > > > > re Hyrum Law, let me quote its first part: > > "With a sufficient number of users of an API..." > > We (Maven project) clearly define what is, and what is not "an API". > > Stop it, please. > > No, no we do not. API is a well understood term of the art in software > development in general and in Java in particular. The Maven project > does not define it. The problem here is precisely that some members > think they can say "pretty please don't use this API that we've marked > public" and have it mean something. If you don't want a method to be > used by client software, don't mark it public. That's the only > distinction that matters. > > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
