On Fri, 28 Aug 2020 at 15:34, Alex Herbert <alex.d.herb...@gmail.com> wrote:
> > On Fri, 28 Aug 2020 at 15:28, sebb <seb...@gmail.com> wrote: > >> On Fri, 28 Aug 2020 at 13:34, Alex Herbert <alex.d.herb...@gmail.com> >> wrote: >> > >> > We have fixed quite a few bugs and added some significant enhancements >> > since Apache Commons Codec 1.14 was released, so I would like to release >> > Apache Commons Codec 1.15. >> > >> > Apache Commons Codec 1.15 RC1 is available for review here: >> > https://dist.apache.org/repos/dist/dev/commons/codec/1.15-RC1 (svn >> > revision 41154 ) >> > >> > The Git tag commons-codec-1.15-RC1 commit for this RC is >> > c89d2af770f05457fbefa5fb4713c888bf177fb2 which you can browse here: >> > >> > >> https://git-wip-us.apache.org/repos/asf?p=commons-codec.git;a=tag;h=refs/tags/commons-codec-1.15-RC1 >> >> Whilst that URL works, it is deprecated, and should be replaced at some >> point. >> Did it come from the component, or is it produced by a separate plugin? >> > > This was generated in by: > > mvn -Prelease org.apache.commons:commons-release-plugin:1.4:vote-txt > > So perhaps something in the pom.xml is configured incorrectly. > > Note I changed some things as that command creates this link: > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1523/org/apache/commons/commons-codec/1.15/ > > But since the groupId is 'commons-codec' and not 'org.apache.commons' the > artifacts are actually here: > > https://repository.apache.org/content/repositories/orgapachecommons-1523/commons-codec/commons-codec/1.15/ > > I do not know if this is something that can be fixed in the pom.xml config > too or if this is for the release plugin. > I used the old release plugin (1.4). Swapping to the latest release plugin: mvn -Prelease org.apache.commons:commons-release-plugin:1.7:vote-txt solves the git-wip reference. So the documentation I was following should be updated: https://commons.apache.org/releases/prepare.html > > > >> >> > Maven artifacts are here: >> > >> > >> https://repository.apache.org/content/repositories/orgapachecommons-1523/commons-codec/commons-codec/1.15/ >> > >> > These are the Maven artifacts and their hashes in Nexus: >> > >> > #Release SHA-512s >> > #Fri Aug 28 13:02:53 BST 2020 >> > >> commons-codec-1.15-bin.tar.gz=b6d517db15aedc424d112b8f3282c63f56aae66adaf317baf9853da65e291eb03fb5da51792aa437c7fdce63f6685c75373265e2a035b51e7525048716d7bfe3 >> > >> commons-codec-1.15-bin.zip=2495a5dcc2e57280882e8bb13972c1881b074e3e06ae13f45025c63e96cdc77c3af2a19f8417dce538172738eee31a3a8ce73227427b4f5db2214f18b71efc7d >> > >> commons-codec-1.15-javadoc.jar=0aac697eb0d11b39013b458aa4ba24e5408b9f1435cbc12ebde9cabe39f8fb8fb37a84737a25b31f88f148cbf69a27c34e65952118cc7356511a1eefeb0a9497 >> > >> commons-codec-1.15-sources.jar=4c451f148d4c4c4f09e93aa12345dcf39e17ccba3c30f638a75a5df3af622e12595946619cb4553dffcc6f77d7ad43b1e216a637942e02da955a376150393804 >> > >> commons-codec-1.15-src.tar.gz=dcf0b86f269a96362dca5b36b9e764a07e390634804b359d4dbd1a0c50bfcc9f778e3797f196e1f553d76dd25b3c6fd016f0ffbbca856fa6c88d3d55791889ce >> > >> commons-codec-1.15-src.zip=41f380634710cc5523426587de0cca7d06ba3b7933f8e1b488c85cbb58fb9e97e0ff48c09f2ae5f09b95f4f4994621d5bf9e60e3c08412b545b4bb6969dfcd95 >> > >> commons-codec-1.15-test-sources.jar=a77c00eb1a9d976b8f53536248a0c08d1e068b1634cf5ae232728ffffff01fd553ff9aa5832538fe99ae0017a0a71e11df86156fb6a576ef88a9c11571129094 >> > >> commons-codec-1.15-tests.jar=3c338b6f4e95d2cec4d16f140f5f4cf4de1ffac6128038bce3058266b7555f037566b6553729d1067caf42770ae1d35726f20837787366014bca5ae86e7f3ba9 >> > >> > >> > I have tested this with 'mvn clean test package site -Pjapicmp' using: >> > >> > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) >> > Maven home: /usr/local/apache-maven-3.6.3 >> > Java version: 1.8.0_265, vendor: Private Build, runtime: >> > /usr/lib/jvm/java-8-openjdk-amd64/jre >> > Default locale: en_GB, platform encoding: UTF-8 >> > OS name: "linux", version: "4.4.0-186-generic", arch: "amd64", family: >> > "unix" >> > >> > Details of changes since 1.14 are in the release notes: >> > >> > >> https://dist.apache.org/repos/dist/dev/commons/codec/1.15-RC1/RELEASE-NOTES.txt >> > >> > >> https://dist.apache.org/repos/dist/dev/commons/codec/1.15-RC1/site/changes-report.html >> > >> > Site: >> > >> > >> https://dist.apache.org/repos/dist/dev/commons/codec/1.15-RC1/site/index.html >> > (note some *relative* links are broken and the 1.15 directories are >> not >> > yet created - these will be OK once the site is deployed.) >> > >> > JApiCmp Report (compared to 1.14): >> > >> > >> https://dist.apache.org/repos/dist/dev/commons/codec/1.15-RC1/site/japicmp.html >> > >> > RAT Report: >> > >> > >> https://dist.apache.org/repos/dist/dev/commons/codec/1.15-RC1/site/rat-report.html >> > >> > KEYS: >> > https://www.apache.org/dist/commons/KEYS >> > >> > Please review the release candidate and vote. >> > This vote will close no sooner that 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, >> > >> > Alex Herbert, >> > Release Manager (using key BC87A3FD0A54480F0BADBEBD21939FF0CA2A6567) >> > >> > For 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-codec.git >> --branch >> > commons-codec-1.15-RC1 commons-codec-1.15-RC1 >> > cd commons-codec-1.15-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 >> > >> > 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- >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >>
