On Tue, 9 Apr 2019 at 13:54, Jochen Wiedmann <jochen.wiedm...@gmail.com> wrote: > > On Tue, Apr 9, 2019 at 2:43 PM sebb <seb...@gmail.com> wrote: > > > Unless I am misunderstanding this, the property value won't be checked > > to see if i is changed when an incompatible versioni s released. > > True, but that applies in either case, as soon as we have module > names, doesn't it?
Not sure which cases you are referring to. We already have a process for ensuring that Maven coords and package names are changed when API breaks. Do we really want to have yet another name that has to be maintained? > So, I'd like to keep this out of the current > discussion, which is (IMO) about how we implement the module name. But what are we trying to achieve here? Being able to define the module name independently is all very well, but it does not solve the problem of ensuring that the module name is correct, and remains correct when code is updated. > Jochen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
