On Tue, 18 Jan 2022 at 00:48, Gilles Sadowski <[email protected]> wrote: > > Hi. > > Is the "dist-archive" module/directory still in use. > I noticed that the command > $ cd dist-archive && mvn assembly::single > (as documented e.g. in [1]) generates "bin" archives (".tar.gz" > and ".zip" files) that only contain the NOTICE and LICENCE > files). The "src" seem OK. > However, I also see that ".tar.gz" and ".zip" archive files[2] are > generated under each module's "target" directory that indeed > contain the expected JAR files. > I thus wonder whether the "dist-archive" is still in use.
The dist-archive module is used in the release profile. It creates the correct assembly archives after the package phase has been run as part of the release phase. This is used by the Commons release plugin. The assembly:single goal is not explicitly used any more. In the release.howto.txt document for RNG this is all under section 12. It states that this section is now all performed by the Commons release plugin. The latest RNG guide has the commands that I used for release 1.4 (Sept 2021) to verify the release plugin did correctly perform the tasks in section 12. So this is a documentation issue. On the next release of a multi-module project (e.g. Numbers) the section can be altered to state what is expected to be performed by the release plugin. The manual steps to do the same thing may not work and can be removed if they are invalid. However they may work if 'mvn package' has been run before the 'assembly:single' goal (I've not checked). Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
