On Tue, Mar 31, 2020 at 4:51 PM Gilles Sadowski <gillese...@gmail.com> wrote:
> Hi. > > Le mar. 31 mars 2020 à 22:30, Gary Gregory <garydgreg...@gmail.com> a > écrit : > > > > On Tue, Mar 31, 2020 at 3:16 PM Gilles Sadowski <gillese...@gmail.com> > > wrote: > > > > > > > [...] > > > > > I'm fine with improving the (common?) convention. > > > > > > > > > > Why not dropping the redundant reference to the component > > > > > and project, since they are in the repo's name? > > > > > And how about focusing on the tag's purpose by mentioning > > > > > it first? > > > > > Thus: > > > > > rc1_v1.0-beta1 > > > > > > > > > > > > > The argument for having the component name in the tag name is that > when > > > you > > > > clone the repo, you get a 'nice' directory name by default. > > > > > > > > > > Convincing. > > > > > > So, I suggest > > > > > > commons-numbers_v1.0-beta1_rc1 > > > > > > > For me, I find the mix of - and _ lame and since we use - in component > > names, I prefer -'s for all separators. > > I beg to differ. > A hyphen is for joining, an underscore for separating, making > the string more parseable (both for humans and for scripts). > That's certainly not how Maven sees it, for example: commons-lang3-3.10-javadoc.jar <https://repo1.maven.org/maven2/org/apache/commons/commons-lang3/3.10/commons-lang3-3.10-javadoc.jar> I'd rather we stick to known conventions and not invent yet another one. Gary > > > > > > i.e. > > > > > > <component id>_v<version>[-beta<m>]_rc<n> > > > > > > OK? > > > > > > Gilles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
