On 25 April 2016 at 09:13, Emmanuel Bourg <ebo...@apache.org> wrote: > Le 25/04/2016 03:04, sebb a écrit : > >> However the distribution naming convention needs to distinguish >> between releases using different Java packages. > > I don't think that's a justified requirement, unless we intent to use > the same version with different packages (for example a version 3.5 of > commons-lang using the old org.apache.commons.lang package, and a > version 3.5 using the new org.apache.commons.lang3 package). This will > never happen.
Never suggests it is impossible; however that is not the case. It hasn't happened yet, but I can imagine that there might be a reason to maintain two parallel release versions. Note that the artifact names themselves use the artifactid. So using it in the folder name would be no different. >> So how do you suggest fixing that problem? > > As I suggested, by not using the artifactId. The options are: > 1. [component]-[version]/ > 2. [version]/ > > The option 2 has my preference (the path already contains the name of > the component, no need to repeat it). There are occasions when having the component name can be useful. For example when checking out the tag for votes. Possibly less of an issue for the dist tree, but I found it a big nuisance when checking out SVN tags for multiple votes. > Emmanuel Bourg > > > --------------------------------------------------------------------- > 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
