I think it's could save us some time if we check the snapshot src
artifact first.
You can always create a source distribution without using maven release command.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Oct 13, 2019 at 9:41 AM Xiangdong Huang <[email protected]> wrote:
>
> Hi Justin,
>
> In my understanding (I am not sure whether my understanding is correct),
> uploading files to the maven Nexus Staging repository is optional...
>
> The only thing we must to do before starting a voting is uploading the
> source-release.zip with its asc and sha512 files  (and the
> binary-distribtuion.zip if wanted) to https://dist.apache.org/repos/dist/dev
> .
>
> There are two ways to generate the source-release.zip:
>
> (1) do it manually, and generate asc and sha512 files manually.
>
> (2) using mvn release:prepare and release:perform command to do that
> automatically (maven will organize files according to the description of
> distribution.xml, copying jars into the lib folder and copying scripts to
> the correct location according to assembly folder and server.xml and
> client.xml)
> The side-effect is that, mvn release command will upload the jars into the
> maven nexus staging repository... (fortunately, users can not observe these
> files before I manually click  "release" button, so that maybe we can bear
> the side-effect)
>
> I think doing it automatically is good. If there is other ways to do that
> automatically, I will try it.
>
> Best,
> -----------------------------------
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Justin Mclean <[email protected]> 于2019年10月13日周日 上午9:04写道:
>
> > Hi,
> >
> > I’m still not sure why you are preparing the maven artefacts before the
> > vote is finished. I guess it good to check that everyone is OK but they can
> > be prepared after as maven is not an official release area.
> >
> > Thanks,
> > Justin

Reply via email to