Hello, I understand the dist module as preparing the artifacts for the binary and source distribution of the ASF download. And I agree that those target files must not be attached to the maven repository. As such the POM can be changed to a POM only module (or manually removed from the repo). In that case the artifact names can be consistently created. Creating the checksum files in this case would be good.
The actual core artifact (and its related src and javadoc archives) in the maven repo are for consumption (by Maven and IDEs). They are different from the -bin and -src artifacts distributed by the download servers. Gruss Bernd -- http://bernd.eckenfels.net -----Original Message----- From: Josh Elser <els...@apache.org> To: Commons Developers List <dev@commons.apache.org> Sent: Di., 24 Mai 2016 4:20 Subject: Re: [VFS] Final steps for 2.1 sebb wrote: > On 22 May 2016 at 03:54, Josh Elser<els...@apache.org> wrote: >> > It's not a problem, it's an inconvenience. >> > >> > Ideally, Maven builds the artifacts with the intended names. This creates >> > consistency through every VOTE message, xsum/sig verification automation, >> > website links, and dist.a.o files. > > Does not follow, see below. > >> > Renaming them by hand just makes things harder, IMO. > > The vote mail should be on the dist/dev archives for the archives > intended for the ASF mirrors and on Nexus for the Maven jars. > The distribution files don't belong in Maven Central and they should > be copied/deleted from Nexus to dist/dev before the vote. > > So there should be no inconsistency. > > The only extra manual stage is the rename which must be done before > the dist/dev files are committed. > > I agree it would be simpler if no rename was involved. > But it does not affect vote consistency. Wasn't implying that the VOTE'd artifacts were inconsistent, just the files are inconsistently named presently. Sorry for not being more specific the first time around. My only point was avoiding the rename at various stages in the release process. I agree with your assessment. --------------------------------------------------------------------- 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
