+1 (nb) On Wed, 25 Dec 2024 at 20:37, Gary Gregory <garydgreg...@gmail.com> wrote: > > To use more and more of the current Maven plugins, we must update > the Apache Commons Skin to Doxia 2. This release accomplishes that. > > Apache Commons Skin 5.0.0 RC1 does not have a Subversion staging directory > (for some reason lost to the sands of time). > > The Git tag commons-skin-5.0.0-RC1 commit for this RC is > c7a0a92b6f21555029ab255b9e3be508202af64b which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-skin.git;a=commit;h=c7a0a92b6f21555029ab255b9e3be508202af64b > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-skin.git --branch > commons-skin-5.0.0-RC1 commons-skin-5.0.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1792/org/apache/commons/commons-skin/5.0.0/ > > I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy -P > jacoco -P japicmp clean package site deploy' using: > > openjdk version "17.0.13" 2024-10-15 > OpenJDK Runtime Environment Homebrew (build 17.0.13+0) > OpenJDK 64-Bit Server VM Homebrew (build 17.0.13+0, mixed mode, sharing) > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec > Java version: 17.0.13, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@17/17.0.13/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "15.2", arch: "aarch64", family: "mac" > > Darwin ****.local 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec 6 19:03:40 > PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041 arm64 > Docker version 27.3.1, build ce12230 > > > Details of changes since 4.2 are in the release notes: > https://github.com/apache/commons-skin/blob/master/RELEASE-NOTES.txt > > Site: > There is no site for this Maven skin. > > RAT Report: > Build the component to check it. Normally, a build fails if some files > are outstanding. > > KEYS: > https://downloads.apache.org/commons/KEYS > > Please review the release candidate and vote. > This vote will close no sooner than 72 hours from now. > > [ ] +1 Release these artifacts > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this release because... > > Thank you, > > Gary Gregory, > Release Manager (using key 86fdc7e2a11262cb) > > The following is intended as a helper and refresher for reviewers. > > Validating a release candidate > ============================== > > These guidelines are NOT complete. > > Requirements: Git, Java, Maven. > > You can validate a release from a release candidate (RC) tag as follows. > > 1) Clone and checkout the RC tag > > git clone https://gitbox.apache.org/repos/asf/commons-skin.git --branch > commons-skin-5.0.0-RC1 commons-skin-5.0.0-RC1 > cd commons-skin-5.0.0-RC1 > > 2) Check Apache licenses > > This step is not required if the site includes a RAT report page which you > then must check. > > mvn apache-rat:check > > 3) Check binary compatibility > > Older components still use Apache Clirr: > > This step is not required if the site includes a Clirr report page which > you then must check. > > mvn clirr:check > > Newer components use JApiCmp with the japicmp Maven Profile: > > This step is not required if the site includes a JApiCmp report page which > you then must check. > > mvn install -DskipTests -P japicmp japicmp:cmp > > 4) Build the package > > mvn -V clean package > > You can record the Maven and Java version produced by -V in your VOTE reply. > To gather OS information from a command line: > Windows: ver > Linux: uname -a > > 5) Build the site for a single module project > > Note: Some plugins require the components to be installed instead of > packaged. > > mvn site > Check the site reports in: > - Windows: target\site\index.html > - Linux: target/site/index.html > > -the end-
-- SÅ‚awomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org