Hi, On Mon, 6 Sept 2021 at 13:13, Matt Juntunen <matt.a.juntu...@gmail.com> wrote:
> The windows build is fixed. Before I cast my vote, can someone remind > me what to do to verify the nexus artifacts? > Thanks for checking. The nexus items are convenience artifacts. IIUC the vote is specifically for the source release. All derived release artifacts are non-essential to the release vote. The link in the vote e-mail for the nexus artifacts was wrong (I did not change it from the auto generated link created by the commons release plugin). Here are the artifacts: https://repository.apache.org/content/repositories/orgapachecommons-1571/org/apache/commons/ A laborious way to verify them is to download them, manually install them or put them on the classpath and then run them in a test application. You can add this repository to a maven project POM and then maven should be able to download them (I've not tried that but may give it a go to check if it's possible). An ideal way to test them would be to run all the unit tests from the source download against the maven artifacts. I do not recall anyone performing these actions on a previous vote. A quick browse of the staged artifacts to check the expected jars are present should be enough. The release guide expects for each module: .pom .jar .javadoc.jar .sources.jar .tests.jar .test-sources.jar The parent POM should also be staged. I did notice that the parent module has a site.xml staged in nexus. This must be a default for any project with the pom packaging as it also happens for commons-parent (you can find this in maven central). I do not know why you would want to include the site.xml as a dependency so perhaps this is something to clean up in the commons release plugin. Alex
