Re: [all] release validation
On 2020-07-12, Rob Tompkins wrote: > given the consistency of the signatures from the plugins…do we need to > check them for releases anymore? Yes, please. Not everybody uses the plugins and even if everybody did a misconfiguration could be pulling in the wrong key or a key not available from the expected download location. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[all] release validation (was: Re: [VOTE] Release Apache Commons Lang 3.11 based on RC2)
given the consistency of the signatures from the plugins…do we need to check them for releases anymore? I have been using shell scripts to validate all of the md5’s, sha1’s, sha512’s, and gpg signatures that come out of the process. @sebb or @markt do you have an opinion here? -Rob > On Jul 12, 2020, at 9:42 AM, Gary Gregory wrote: > > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Lang 3.10 was released, so I would like to release > Apache Commons Lang 3.11. > > Apache Commons Lang 3.11 RC2 is available for review here: >https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2 (svn > revision 40434) > > The Git tag commons-lang-3.11-RC2 commit for this RC is > f62f0f59a33d2c42bd4236ea7122735de30d91fc which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=f62f0f59a33d2c42bd4236ea7122735de30d91fc > You may checkout this tag using: >git clone https://gitbox.apache.org/repos/asf/commons-lang.git --branch > commons-lang-3.11-RC2 commons-lang-3.11-RC2 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1506/org/apache/commons/commons-lang3/3.11/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Jul 12 09:31:57 EDT 2020 > commons-lang3-3.11-bin.tar.gz=314ed5b2a0af658a008b0c6dbba0c79c8e465a413fa483b68eaa7d60ef6731ca12bd04fc5a1e7c4faab4eedfca48b1ebc51228dc4bbcc44287aac6805e41d8a1 > commons-lang3-3.11-bin.zip=e2406057b664b2c2230f8804ed442c72e28ab93e01cca1d46d4dbbd5b179f0fbc1f02218654b459718f483210cb5e3f8621d4f3c31f0b3bb3ff05f8913e18f6c > commons-lang3-3.11-javadoc.jar=ccba8259d8eb75c721145d0da24e04ccc20af485f010db424eae33e5b2563f878e03b498b5a8bb3db637ac1db5e14868f7356412f8679f6ce6ed82d9a0a62f4d > commons-lang3-3.11-sources.jar=b9c210c4c78823b5eb50f420791a0d6515bc8413bfff029d678aeea78331bba1c127557c0f67667c467a1f66b79806cc5ca18668e3ca55048eb50aaeccaea3e3 > commons-lang3-3.11-src.tar.gz=ebcb13e47c24e6984835d9d6904fe33077aa3ba781cd61db109fa7005517e4e74cf086c4789a1d65cf3d6c4924b32337c98827a75f91aab908d8e8b9d3b92087 > commons-lang3-3.11-src.zip=2c7f44f9a5c8d597595bdcd54905e08cf10260f265e194cb62c5142cd2573c2a59660f01760ff39442febf90e0c75aa377f91fc071fb1ab7bbc55c1476a9c363 > commons-lang3-3.11-test-sources.jar=93345fb5a4c148eaad3d814973520640fae5fde8e4c72eafade846dc557301b1569f07ad1cd4a6bf81e8893846388208cf36addec40a2d2d1fa8fd18ad112b49 > commons-lang3-3.11-tests.jar=a168e088e9993dcad96fe689d2a13d384b36b8dc93f19a92a34c93add3ce14388e8031d75bb378c0ebb30ec625d1a27e106c28a1a3f9001d5bf5b7c5cebde123 > > I have tested this with: > > mvn -V -Duser.name=%my_apache_id% > -Dcommons.release-plugin.version=%commons.release-plugin.version% -Prelease > -Ptest-deploy -P jacoco -P japicmp clean package site deploy > > using: > > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > Maven home: C:\Java\apache-maven-3.6.3\bin\.. > Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program > Files\Java\jdk1.8.0_251\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" > > Details of changes since 3.10 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/site/index.html >(note some *relative* links are broken and the 3.11 directories are not > yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 3.10): > > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/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, > > Gary Gregory, > Release Manager (using key 86fdc7e2a11262cb) > > 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-lang.git --branch > commons-lang-3.11-RC2 commons-lang-3.11-RC2 > cd commons-lang-3.11-RC2 > > 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
Re: [exec] Update from Java 5 to 6
I am ok with Java 8 as the requirement. Gary On Sun, Jul 12, 2020, 06:16 T. Schapitz wrote: > Hi there, > > maybe a bit late in the game, because the original post regarding this > topic was 9 months ago, but i think there is a good case for skipping > directly to JDK 8: > > If we opt for utilizing not only the java.lang.ProcessBuilder introduced > in JDK 1.5, but also the additional methods for stream inheritance and > stream redirection(*) introduced in 6 & 7, this will likely be done by > introducing additional methods into the API interfaces, whether it is > the CommandLauncher or the Executor. But this could potentially break > backward compatibility for users of common-exec, that implemented those > interfaces. (Granted, it's rather unlikely somebody did this - most > would rather be extending DefaultExecutor). But problems like this could > easily avoided by adding default implementations introduced with JDK 8. > > Btw: who would be reviewing a pull request, if I had one? Is currently > somebody reviewing working on the issues? > > (I'm just trying to get a feel for the project, and want to avoid > duplication) > > Thomas > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org
[VOTE] Release Apache Commons Lang 3.11 based on RC2
We have fixed quite a few bugs and added some significant enhancements since Apache Commons Lang 3.10 was released, so I would like to release Apache Commons Lang 3.11. Apache Commons Lang 3.11 RC2 is available for review here: https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2 (svn revision 40434) The Git tag commons-lang-3.11-RC2 commit for this RC is f62f0f59a33d2c42bd4236ea7122735de30d91fc which you can browse here: https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=f62f0f59a33d2c42bd4236ea7122735de30d91fc You may checkout this tag using: git clone https://gitbox.apache.org/repos/asf/commons-lang.git --branch commons-lang-3.11-RC2 commons-lang-3.11-RC2 Maven artifacts are here: https://repository.apache.org/content/repositories/orgapachecommons-1506/org/apache/commons/commons-lang3/3.11/ These are the artifacts and their hashes: #Release SHA-512s #Sun Jul 12 09:31:57 EDT 2020 commons-lang3-3.11-bin.tar.gz=314ed5b2a0af658a008b0c6dbba0c79c8e465a413fa483b68eaa7d60ef6731ca12bd04fc5a1e7c4faab4eedfca48b1ebc51228dc4bbcc44287aac6805e41d8a1 commons-lang3-3.11-bin.zip=e2406057b664b2c2230f8804ed442c72e28ab93e01cca1d46d4dbbd5b179f0fbc1f02218654b459718f483210cb5e3f8621d4f3c31f0b3bb3ff05f8913e18f6c commons-lang3-3.11-javadoc.jar=ccba8259d8eb75c721145d0da24e04ccc20af485f010db424eae33e5b2563f878e03b498b5a8bb3db637ac1db5e14868f7356412f8679f6ce6ed82d9a0a62f4d commons-lang3-3.11-sources.jar=b9c210c4c78823b5eb50f420791a0d6515bc8413bfff029d678aeea78331bba1c127557c0f67667c467a1f66b79806cc5ca18668e3ca55048eb50aaeccaea3e3 commons-lang3-3.11-src.tar.gz=ebcb13e47c24e6984835d9d6904fe33077aa3ba781cd61db109fa7005517e4e74cf086c4789a1d65cf3d6c4924b32337c98827a75f91aab908d8e8b9d3b92087 commons-lang3-3.11-src.zip=2c7f44f9a5c8d597595bdcd54905e08cf10260f265e194cb62c5142cd2573c2a59660f01760ff39442febf90e0c75aa377f91fc071fb1ab7bbc55c1476a9c363 commons-lang3-3.11-test-sources.jar=93345fb5a4c148eaad3d814973520640fae5fde8e4c72eafade846dc557301b1569f07ad1cd4a6bf81e8893846388208cf36addec40a2d2d1fa8fd18ad112b49 commons-lang3-3.11-tests.jar=a168e088e9993dcad96fe689d2a13d384b36b8dc93f19a92a34c93add3ce14388e8031d75bb378c0ebb30ec625d1a27e106c28a1a3f9001d5bf5b7c5cebde123 I have tested this with: mvn -V -Duser.name=%my_apache_id% -Dcommons.release-plugin.version=%commons.release-plugin.version% -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy using: Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: C:\Java\apache-maven-3.6.3\bin\.. Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_251\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" Details of changes since 3.10 are in the release notes: https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/RELEASE-NOTES.txt https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/site/changes-report.html Site: https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/site/index.html (note some *relative* links are broken and the 3.11 directories are not yet created - these will be OK once the site is deployed.) JApiCmp Report (compared to 3.10): https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/site/japicmp.html RAT Report: https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC2/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, Gary Gregory, Release Manager (using key 86fdc7e2a11262cb) 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-lang.git --branch commons-lang-3.11-RC2 commons-lang-3.11-RC2 cd commons-lang-3.11-RC2 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
Re: [CANCEL][VOTE] Release Apache Commons Lang 3.11 based on RC1
On Sun, Jul 12, 2020 at 8:53 AM Rob Tompkins wrote: > After some very minor changes and citation additions to the javadoc. I > think we’re likely ready. > Thank Rob, I'll roll RC2. Gary > > Cheers, > -Rob > > > On Jul 11, 2020, at 3:50 PM, Gary Gregory > wrote: > > > > Not fully baked, cancelling due to an issue discovered by Rob. > > > > Gary > > > > On Fri, Jul 10, 2020 at 7:58 PM Gary Gregory > wrote: > > > >> We have fixed quite a few bugs and added some significant enhancements > >> since Apache Commons Lang 3.10 was released, so I would like to release > >> Apache Commons Lang 3.11. > >> > >> Apache Commons Lang 3.11 RC1 is available for review here: > >>https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1 (svn > >> revision 40422) > >> > >> The Git tag commons-lang-3.11-RC1 commit for this RC is > >> ac1070e84e42acf3c2ada36e4727c2d99b0fc48e which you can browse here: > >> > >> > https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=ac1070e84e42acf3c2ada36e4727c2d99b0fc48e > >> You may checkout this tag using: > >>git clone https://gitbox.apache.org/repos/asf/commons-lang.git > >> --branch commons-lang-3.11-RC1 commons-lang-3.11-RC1 > >> > >> Maven artifacts are here: > >> > >> > https://repository.apache.org/content/repositories/orgapachecommons-1504/org/apache/commons/commons-lang3/3.11/ > >> > >> These are the artifacts and their hashes: > >> > >> #Release SHA-512s > >> #Fri Jul 10 19:48:00 EDT 2020 > >> > >> > commons-lang3-3.11-bin.tar.gz=d205b63c1dd9b0125b395c4523d418057162865292d43dd4cb12bd697ef56ff0519c406e1141e50d217b4ad3e1a0c9cd8f28ae032f596662d9729c44fa00b927 > >> > >> > commons-lang3-3.11-bin.tar.gz.asc=9326796e4cbfd11f995adad25ebf27bbddc178473ab417df6fc89580a4fb97a6d620dbe91d6d1f74fc3c86283e6896ba00cb9c57285060e4d6c58c20a49734e9 > >> > >> > commons-lang3-3.11-bin.zip=61f7151b72f28f07aa4f432a5b9926f814b3c2383db7ad23670bd6dbffb7f7cf9cfec2b7b69398fa890ce2846cb64bd3994277a9e844d0df31618abe4a67e051 > >> > >> > commons-lang3-3.11-javadoc.jar=835ebb0838e113ad1d3ef09af4eb6b6b5ed8228517fa781083ba266cc59cd1421eb2967abe4e421c0d93c146cd07c44bf73e45968f0c41859a9abc3736f3c534 > >> > >> > commons-lang3-3.11-sources.jar=2fbef340a2f435d19ddc705f5faa97bb14335c13c9071555405b6a1bd7245da1cfbed8c018e9ae744f271f366328b980474b23c906dd3f5cf8839c0e972648d2 > >> > >> > commons-lang3-3.11-src.tar.gz=0a8d5857a0614d4799358b49a2a452b86a8883157daeeb0e112008e3792bae3e039fcc47253e48ef9ae8e9561a75205593ee959845ff70fbf7baa6030f55d691 > >> > >> > commons-lang3-3.11-src.zip=9c8468396998c25f2ec2a53ed7f5dc067ab1a2e9333bff797bf1979a1fabad464725dcb4c244622ef2fb0fa4d378f88446e200bec101f3541da52d9a79f3fcec > >> > >> > commons-lang3-3.11-test-sources.jar=c3356a1de3c157236d326d8907ff840dae9b6b32c846c7180804623d55d0c701d5b07d4c6298b631c5b9db75949d8d489cfc233c559a1533a2b17b97c524c603 > >> > >> > commons-lang3-3.11-tests.jar=2e77319ec9c0485185ae965bee9c60d25a09476bbc122d2f810f38ad7f9278ce031a92aacdd17c2b5181772d4d0517770d38afb0b013208926b2ef459853794e > >> > >> I have tested this with 'mvn -V -Duser.name=%my_apache_id% > >> -Dcommons.release-plugin.version=%commons.release-plugin.version% > -Prelease > >> -Ptest-deploy -P jacoco -P japicmp clean package site deploy' using: > >> > >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > >> Maven home: C:\Java\apache-maven-3.6.3\bin\.. > >> Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program > >> Files\Java\jdk1.8.0_251\jre > >> Default locale: en_US, platform encoding: Cp1252 > >> > >> Details of changes since 3.10 are in the release notes: > >> > >> > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1/RELEASE-NOTES.txt > >> > >> > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1/site/changes-report.html > >> > >> Site: > >> > >> > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1/site/index.html > >>(note some *relative* links are broken and the 3.11 directories are > >> not yet created - these will be OK once the site is deployed.) > >> > >> JApiCmp Report (compared to 3.10): > >> > >> > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1/site/japicmp.html > >> > >> RAT Report: > >> > >> > https://dist.apache.org/repos/dist/dev/commons/lang/3.11-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, > >> > >> Gary Gregory, > >> Release Manager (using key 86fdc7e2a11262cb) > >> > >> 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
Re: [CANCEL][VOTE] Release Apache Commons Lang 3.11 based on RC1
After some very minor changes and citation additions to the javadoc. I think we’re likely ready. Cheers, -Rob > On Jul 11, 2020, at 3:50 PM, Gary Gregory wrote: > > Not fully baked, cancelling due to an issue discovered by Rob. > > Gary > > On Fri, Jul 10, 2020 at 7:58 PM Gary Gregory wrote: > >> We have fixed quite a few bugs and added some significant enhancements >> since Apache Commons Lang 3.10 was released, so I would like to release >> Apache Commons Lang 3.11. >> >> Apache Commons Lang 3.11 RC1 is available for review here: >>https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1 (svn >> revision 40422) >> >> The Git tag commons-lang-3.11-RC1 commit for this RC is >> ac1070e84e42acf3c2ada36e4727c2d99b0fc48e which you can browse here: >> >> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=ac1070e84e42acf3c2ada36e4727c2d99b0fc48e >> You may checkout this tag using: >>git clone https://gitbox.apache.org/repos/asf/commons-lang.git >> --branch commons-lang-3.11-RC1 commons-lang-3.11-RC1 >> >> Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapachecommons-1504/org/apache/commons/commons-lang3/3.11/ >> >> These are the artifacts and their hashes: >> >> #Release SHA-512s >> #Fri Jul 10 19:48:00 EDT 2020 >> >> commons-lang3-3.11-bin.tar.gz=d205b63c1dd9b0125b395c4523d418057162865292d43dd4cb12bd697ef56ff0519c406e1141e50d217b4ad3e1a0c9cd8f28ae032f596662d9729c44fa00b927 >> >> commons-lang3-3.11-bin.tar.gz.asc=9326796e4cbfd11f995adad25ebf27bbddc178473ab417df6fc89580a4fb97a6d620dbe91d6d1f74fc3c86283e6896ba00cb9c57285060e4d6c58c20a49734e9 >> >> commons-lang3-3.11-bin.zip=61f7151b72f28f07aa4f432a5b9926f814b3c2383db7ad23670bd6dbffb7f7cf9cfec2b7b69398fa890ce2846cb64bd3994277a9e844d0df31618abe4a67e051 >> >> commons-lang3-3.11-javadoc.jar=835ebb0838e113ad1d3ef09af4eb6b6b5ed8228517fa781083ba266cc59cd1421eb2967abe4e421c0d93c146cd07c44bf73e45968f0c41859a9abc3736f3c534 >> >> commons-lang3-3.11-sources.jar=2fbef340a2f435d19ddc705f5faa97bb14335c13c9071555405b6a1bd7245da1cfbed8c018e9ae744f271f366328b980474b23c906dd3f5cf8839c0e972648d2 >> >> commons-lang3-3.11-src.tar.gz=0a8d5857a0614d4799358b49a2a452b86a8883157daeeb0e112008e3792bae3e039fcc47253e48ef9ae8e9561a75205593ee959845ff70fbf7baa6030f55d691 >> >> commons-lang3-3.11-src.zip=9c8468396998c25f2ec2a53ed7f5dc067ab1a2e9333bff797bf1979a1fabad464725dcb4c244622ef2fb0fa4d378f88446e200bec101f3541da52d9a79f3fcec >> >> commons-lang3-3.11-test-sources.jar=c3356a1de3c157236d326d8907ff840dae9b6b32c846c7180804623d55d0c701d5b07d4c6298b631c5b9db75949d8d489cfc233c559a1533a2b17b97c524c603 >> >> commons-lang3-3.11-tests.jar=2e77319ec9c0485185ae965bee9c60d25a09476bbc122d2f810f38ad7f9278ce031a92aacdd17c2b5181772d4d0517770d38afb0b013208926b2ef459853794e >> >> I have tested this with 'mvn -V -Duser.name=%my_apache_id% >> -Dcommons.release-plugin.version=%commons.release-plugin.version% -Prelease >> -Ptest-deploy -P jacoco -P japicmp clean package site deploy' using: >> >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) >> Maven home: C:\Java\apache-maven-3.6.3\bin\.. >> Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program >> Files\Java\jdk1.8.0_251\jre >> Default locale: en_US, platform encoding: Cp1252 >> >> Details of changes since 3.10 are in the release notes: >> >> https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1/RELEASE-NOTES.txt >> >> https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1/site/changes-report.html >> >> Site: >> >> https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1/site/index.html >>(note some *relative* links are broken and the 3.11 directories are >> not yet created - these will be OK once the site is deployed.) >> >> JApiCmp Report (compared to 3.10): >> >> https://dist.apache.org/repos/dist/dev/commons/lang/3.11-RC1/site/japicmp.html >> >> RAT Report: >> >> https://dist.apache.org/repos/dist/dev/commons/lang/3.11-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, >> >> Gary Gregory, >> Release Manager (using key 86fdc7e2a11262cb) >> >> 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-lang.git --branch >> commons-lang-3.11-RC1 commons-lang-3.11-RC1 >> cd commons-lang-3.11-RC1 >> >> 2) Check Apache licenses >> >> This step is not required if the site
Re: [exec] Update from Java 5 to 6
for 1.5 to 1.6: Seems only 1.6 users can benefit from that...does it worth? for 1.5 to 1.8: GREAATE! +1 for it. T. Schapitz 于2020年7月12日周日 下午6:16写道： > Hi there, > > maybe a bit late in the game, because the original post regarding this > topic was 9 months ago, but i think there is a good case for skipping > directly to JDK 8: > > If we opt for utilizing not only the java.lang.ProcessBuilder introduced > in JDK 1.5, but also the additional methods for stream inheritance and > stream redirection(*) introduced in 6 & 7, this will likely be done by > introducing additional methods into the API interfaces, whether it is > the CommandLauncher or the Executor. But this could potentially break > backward compatibility for users of common-exec, that implemented those > interfaces. (Granted, it's rather unlikely somebody did this - most > would rather be extending DefaultExecutor). But problems like this could > easily avoided by adding default implementations introduced with JDK 8. > > Btw: who would be reviewing a pull request, if I had one? Is currently > somebody reviewing working on the issues? > > (I'm just trying to get a feel for the project, and want to avoid > duplication) > > Thomas > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org
[exec] Update from Java 5 to 6
Hi there, maybe a bit late in the game, because the original post regarding this topic was 9 months ago, but i think there is a good case for skipping directly to JDK 8: If we opt for utilizing not only the java.lang.ProcessBuilder introduced in JDK 1.5, but also the additional methods for stream inheritance and stream redirection(*) introduced in 6 & 7, this will likely be done by introducing additional methods into the API interfaces, whether it is the CommandLauncher or the Executor. But this could potentially break backward compatibility for users of common-exec, that implemented those interfaces. (Granted, it's rather unlikely somebody did this - most would rather be extending DefaultExecutor). But problems like this could easily avoided by adding default implementations introduced with JDK 8. Btw: who would be reviewing a pull request, if I had one? Is currently somebody reviewing working on the issues? (I'm just trying to get a feel for the project, and want to avoid duplication) Thomas pEpkey.asc Description: application/pgp-keys - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
