Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc2

Hi Gary, > Am 20.04.2024 um 15:30 schrieb Gary D. Gregory : > > Something is wrong with at least one ASC file: > https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/commons-jcs3-dist-3.2.1-src.zip.asc > > $ gpg --verify commons-jcs3-dist-3.2.1-src.zip.asc > gpg: assuming signed data

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc2

My vote. > Am 20.04.2024 um 12:25 schrieb Thomas Vandahl : > > Hi folks, > > We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I > would like to release Apache Commons JCS 3.2.1. > > Apache Commons JCS 3.2.1 rc2 is available for review here: >

[VOTE] Release Apache Commons JCS 3.2.1 based on rc2

Hi folks, We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I would like to release Apache Commons JCS 3.2.1. Apache Commons JCS 3.2.1 rc2 is available for review here: https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2 (svn revision 68673) The Git tag

Re: [jcs] multicast issues, was: Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary > Am 07.04.2024 um 20:54 schrieb Gary D. Gregory : > > Hi Thomas, > > OK, here we go: > > VPN on (Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for > Windows x64) > git checkout fe20ca994803b353c32fd0909621d822ee26263c > mvn clean test

[jcs] multicast issues, was: Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

(trying to move this out of the vote thread) Hi Gary, > Am 07.04.2024 um 14:33 schrieb Gary D. Gregory : > > Hi Thomas, > > Ran: > > mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest > > Log: > > https://paste.apache.org/1hmkb Thank you. Could you please make sure that you are at commit

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Sebastian > Am 06.04.2024 um 15:38 schrieb sebb : > > Another minor issue: > If you run 'mvn test' without first doing 'mvn clean', it fails with: > > [ERROR] JDBCDiskCacheUnitTest.testInitializePoolAccess_withPoolName:157 > » SQL Table already exists: JCSTESTTABLE_INITIALIZEPOOLACCESS in

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 06.04.2024 um 17:20 schrieb Gary D. Gregory : > > Switching to origin/release-3.2.1 lets me run the default Maven goal (just > 'mvn') to successfully to completion! > May I kindly ask for the debug log again? I'd like to know whether JCS can find a valid multicast interface

Re: (commons-jcs) 03/03: Skip multicast tests when no multicast interface is available

Hi Gary, > Am 06.04.2024 um 19:35 schrieb Gary Gregory : > > This is where you want to use JUnit assumptions so you get visibility for > skipped tests. > Yes, I know. However, that does not work with the old JUnit3-style tests. I will fix this in the master branch where all tests already have

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 06.04.2024 um 17:48 schrieb Gary D. Gregory : > > And to confirm that VPN is the issue, I reconnected and got: > > [ERROR] Failures: > [ERROR] UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:116 > message not received > [ERROR]

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 06.04.2024 um 17:20 schrieb Gary D. Gregory : > > Ah, I was on git master on Windows, which without the VPN, now hangs in: > > [INFO] Running > org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCacheConcurrentNoDeadLockUnitTest > Thou shalt not run the whole test suite

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 06.04.2024 um 15:07 schrieb Gary D. Gregory : > > mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest > > which failed with the log here: https://paste.apache.org/b4p09 Please check out from branch release-3.2.1 and try again. Bye, Thomas

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 06.04.2024 um 15:07 schrieb Gary D. Gregory : > > mvn test -Dtest=UDPDiscoverySenderEncryptedUnitTest > > which failed with the log here: https://paste.apache.org/b4p09 Thanks for helping me to tackle this. I see that the network interface used for the test is a "Cisco

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 06.04.2024 um 14:10 schrieb Gary D. Gregory : > > Hi Thomas, > > I ran: > > mvn test -Dtest=UDPDiscoverySenderUnitTest -X >\test\out.txt > > and killed it after 10 minutes since it never finished. I tried 3 times. Thanks. Not good. Could you please repeat the test with the log

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 05.04.2024 um 17:28 schrieb Gary D. Gregory : > > [INFO] Running > org.apache.commons.jcs3.utils.discovery.UDPDiscoverySenderEncryptedUnitTest > [ERROR] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 9.526 > s <<< FAILURE! - in >

[CANCEL][VOTE] Release Apache Commons JCS 3.2.1 based on rc1

I am cancelling the vote because of strange test failures in some environments. Bye, Thomas > Am 04.04.2024 um 16:49 schrieb Thomas Vandahl : > > Hi folks, > > We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I > would like to release Apache

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi folks, > Am 05.04.2024 um 23:26 schrieb Gary Gregory : > > Wow, that's the first macOS failure for this type of issue. Bruno and I > both see this on Windows. Ok, let's try to fix this. Could you please run the affected test only with debug log and provide the log files to me? I'll cancel

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 04.04.2024 um 22:30 schrieb Gary D. Gregory : > > After being successful on macOS, I am seeing the following _repeatable_ > failures on Windows 10 running the default Maven goal (just `mvn`): > > ... > [INFO] Running >

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Bruno, > Am 04.04.2024 um 21:46 schrieb Bruno Kinoshita : > > Failed to collect > dependencies at org.apache.openjpa:openjpa:jar:2.4.3 -> > org.apache.openjpa:openjpa-kernel:jar:2.4.3 -> > com.ibm.websphere:websphere_uow_api:jar:0.0.1: Failed to read artifact > descriptor for

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 04.04.2024 um 22:22 schrieb Gary Gregory : > > Another note: > > The changes.xml contains XML not supported by the VM file, for > example, all of the JIRA issue IDs are lost. > I see working JIRA links in

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 04.04.2024 um 22:05 schrieb Gary Gregory : > > I think it is better to keep the release notes as a _history_ instead > of only the latest. This lets you see what you're getting when > migrating from several versions back. I don't quite get your point, I'm afraid. Isn't this what

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 04.04.2024 um 21:59 schrieb Gary Gregory : > > Note that the parent pom is way behind in versions but I am not sure > it matters here (aside from not getting JPMS modules almost for free). Yes, again: intentional. This being a bug fix release for 3.2, I did not want to change too

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi Gary, > Am 04.04.2024 um 21:58 schrieb Gary Gregory : > > Hi Thomas, > > Thank you for preparing a release candidate. > > Something looks confusing in the source tree: > > In git master marked as version 3.2.2-SNAPSHOT, all of the Maven > modules follow the normal naming convention where

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

My vote: > Am 04.04.2024 um 16:49 schrieb Thomas Vandahl : > > Hi folks, > > We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I > would like to release Apache Commons JCS 3.2.1. > > [X] +1 Release these artifacts > [ ] +0 OK, but... > [

[VOTE] Release Apache Commons JCS 3.2.1 based on rc1

Hi folks, We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I would like to release Apache Commons JCS 3.2.1. Apache Commons JCS 3.2.1 rc1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1 (svn revision 68312) The Git tag

Re: [VOTE] Release Apache Commons Compress 1.25.0 based on RC1

> [X] +1 Release these artifacts Signatures ok, build and tests run fine, site and reports look good. Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537) Maven home: /Users/thomas/Dev/apache-maven-3.8.4 Java version: 17.0.8, vendor: Oracle Corporation, runtime:

[JCS] Advice sought on releasing just core

Hi folks, would it be considered good practice to release just one sub-component (commons-jcs3-core) of the project to fix bugs? All other components are unaffected. What would be the release artefact to vote on? Please advise. Bye, Thomas

[JCS] Could please anyone with access to bugs.openjdk.java.net help me documenting a bug fix?

Hi folks, In JCS I just fixed a bug that was caused by a changed JDK behaviour when handling remote exported methods. The change reportedly was a fix for https://bugs.openjdk.java.net/browse/JDK-8230967 This ticket, unfortunately, is not publicly available. I would like to document the JDK

[ANNOUNCEMENT] Apache Commons JCS 3.2 Released

the Apache Commons JCS website: https://commons.apache.org/proper/commons-jcs/ Download it from https://commons.apache.org/proper/commons-jcs/download_jcs.cgi Thomas Vandahl Apache Commons Team - To unsubscribe, e-mail: dev

[RESULT][VOTE] Release Apache Commons JCS 3.2 based on rc1 (2nd round with fixed links)

This vote passes with the following binding +1 votes: - Henri Biestro - Rob Tompkins - Gary Gregory - Thomas Vandahl Thanks to all the voters. I will proceed with the publication. Bye, Thomas > Am 16.09.2023 um 13:41 schrieb Rob Tompkins : > > +1 > Signatures validate properly &

JCS vote

Hi folks, Could some kind soul please find some time to vote on the release 3.2 of JCS? Perhaps this weekend? We would need one more PMC vote. Thank you! Bye, Thomas - To unsubscribe, e-mail:

Re: [VOTE] Release Apache Commons JCS 3.2 based on rc1 (2nd round with fixed links)

Could I have one more (positive :-) PMC vote please? > Am 03.09.2023 um 17:51 schrieb Thomas Vandahl : > > We have fixed quite a few bugs and added some significant enhancements since > Apache Commons JCS 3.1 was released, so I would like to release Apache > Commons JCS 3

Re: [VOTE] Release Apache Commons JCS 3.2 based on rc1 (2nd round with fixed links)

> Please review the release candidate and vote. > This vote will close no sooner than 72 hours from now. > > [X] +1 Release these artifacts > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this release because... My vote Bye, Thomas

[VOTE] Release Apache Commons JCS 3.2 based on rc1 (2nd round with fixed links)

https://www.apache.org/dist/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, Thomas Vandahl (

[CANCEL]: [VOTE] Release Apache Commons JCS 3.2 based on rc1

Will need to fix some links in the vote mail. > Am 22.08.2023 um 15:14 schrieb Thomas Vandahl : > > We have fixed quite a few bugs and added some significant enhancements since > Apache Commons JCS 3.1 was released, so I would like to release Apache > Commons JCS 3.2. > &g

Re: [JCS] GitHub builds broken and Java 17

Hi Gary, > Am 26.08.2023 um 19:58 schrieb Gary Gregory : > > Does anyone know why it's broken? If anyone broke it, that was me. I tried to fix the build configurations but I simply don't understand what there doing. I never put them up in the first place. > And why is was switched to Java 17

Re: [JCS] GitHub builds broken and Java 17

Hi Gary, > Am 26.08.2023 um 19:58 schrieb Gary Gregory : > > Does anyone know why it's broken? If anyone broke it, that was me. I tried to fix the build configurations but I simply don't understand what there doing. I never put them up in the first place. > And why is was switched to Java 17

Re: [VOTE] Release Apache Commons JCS 3.2 based on rc1

Hi Gary, > Am 22.08.2023 um 15:58 schrieb Gary Gregory : > > Something went wrong somewhere because the tag in this email points to a > 3.3-SNAPSHOT version instead of 3.2: > >> The Git tag commons-jcs-3.2-rc1 commit for this RC is > eb9c5b36b48f2b6f45fba7986d46c7006cfb5c4c which you can browse

Re: [VOTE] Release Apache Commons JCS 3.2 based on rc1

> Am 22.08.2023 um 15:14 schrieb Thomas Vandahl : > > We have fixed quite a few bugs and added some significant enhancements since > Apache Commons JCS 3.1 was released, so I would like to release Apache > Commons JCS 3.2. ... > [X] +1 Release these artifacts > [ ] +0

[VOTE] Release Apache Commons JCS 3.2 based on rc1

-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 than 72 hours from now. [ ] +1 Release these artifacts [ ] +0 OK, but... [ ] -0 OK, but really should fix... [ ] -1 I oppose this release because...

Re: [VOTE][LAZY] Release Apache Commons Parent 57 based on RC1

Hi Gary, > Am 22.04.2023 um 16:24 schrieb Gary Gregory >: > > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Parent 56 was released, so I would like to > release Apache Commons Parent 57. > Can we please make the

Re: [VOTE][LAZY] Release Apache Commons Parent 57 based on RC1

Hi Gary, > Am 22.04.2023 um 16:24 schrieb Gary Gregory : > > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Parent 56 was released, so I would like to > release Apache Commons Parent 57. > Can we please make the commons-release-plugin an optional

Re: [parent][release][rng] Issue with release plugin multi-module builds

> Am 28.09.2022 um 14:24 schrieb Alex Herbert : > > So CP 53 behaviour was for this flag to be false. Now in CP 54 this flag is > true. Thus all multi-module builds should set this flag to false in all > non-distribution modules. > > Q. Should these properties be present in CP? They have never

Re: [ALL] Don't update ossf/scorecard-action

Hi Gary > Am 28.09.2022 um 21:31 schrieb Gary Gregory : > > A specific version of the ossf/scorecard-action is approved by Apache Infra. Is there any discussion I might have missed why this is required now? Bye, Thomas - To

Re: [VOTE] Release Apache Commons Imaging 1.0-alpha3 based on RC2

Hi Bruno, > Am 13.05.2022 um 14:02 schrieb Bruno Kinoshita : > > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Imaging 1.0-alpha2 was released, so I would like to > release Apache Commons Imaging 1.0-alpha3. > > Apache Commons Imaging 1.0-alpha3

Re: [VOTE] Release Apache Commons Imaging 1.0-alpha3 based on RC1

Hi Bruno > Am 13.05.2022 um 07:26 schrieb Bruno Kinoshita : > > https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1 > You may checkout this tag using: >git clone https://gitbox.apache.org/repos/asf/commons-imaging.git > --branch

[ANNOUNCE] Apache Commons JCS 3.1

The Apache Commons project announces the release of Apache Commons JCS 3.1. Apache Commons JCS is a distributed caching system written in Java. It is intended to speed up applications by providing a means to manage cached data of various dynamic natures. JCS 3.0 and onwards require at least

[RESULT][VOTE] Release Apache Commons JCS 3.1 based on rc2

Hi folks, > Am 03.01.2022 um 18:24 schrieb Thomas Vandahl : > > Please review the release candidate and vote. This vote passes with the following votes: Gilles Sadowski: +1 Bruno Kinoshita: +1 Thomas Vandahl: +1 I’ll go ahead with the release publication. Thanks to the voters. By

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

Hi Gilles, > Am 17.01.2022 um 14:11 schrieb Gilles Sadowski : > > No; the remark is for making the reviewer's life easier, i.e just copy/paste > the command and see the build succeed. Without the environment variable, > the "javadoc" step fails IIRC. Ok, thanks for the hint. I didn’t know

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

Hi Gilles, > Am 17.01.2022 um 14:11 schrieb Gilles Sadowski : > > No; the remark is for making the reviewer's life easier, i.e just copy/paste > the command and see the build succeed. Without the environment variable, > the "javadoc" step fails IIRC. Ok, thanks for the hint. I didn’t know

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

Hi Gilles, > Am 14.01.2022 um 15:37 schrieb Gilles Sadowski : > >>> Maven artifacts are here: >>> >>> https://repository.apache.org/content/repositories/orgapachecommons-1576/org/apache/commons/commons-jcs3/3.1/ > > I only see one ".pom" file and one ".xml" file (with their respective >

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

Hi folks, could I please have one more PMC vote? If you think that the outputTimestamp issue must be fixed before, then please vote -1 explicitly. Bye, Thomas > Am 03.01.2022 um 18:24 schrieb Thomas Vandahl : > > Hi folks, > > We have fixed quite a few bugs and added s

[all] project.build.outputTimestamp set in org.apache:apache, was Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

Hi folks, This may be of general interest, at least I had no idea about the consequences. So I thought I’d share the result of my research. > Am 06.01.2022 um 10:30 schrieb Thomas Vandahl : > >> Maybe somebody else knows how that can happen. > The effective POM shows the followin

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

Hi Bruno, > Am 05.01.2022 um 21:59 schrieb Bruno P. Kinoshita > : > > Did you have an old NOTICE file in the directory where you built the jcs > release? I read the release instructions [1] and the code of > commons-release-plugin [2], and found nothing that appeared to replace files > or

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

Hi Bruno, > Am 05.01.2022 um 06:41 schrieb Bruno P. Kinoshita > : > > I didn't have much time, so inspected only one file, randomly selected, from > the dist area. The src zip. @Thomas, I think the NOTICE has the date 2020? I > think that can be fixed later? Everything else looks OK in that

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

> Am 03.01.2022 um 18:24 schrieb Thomas Vandahl : > > Hi folks, > > We have fixed quite a few bugs and added some significant enhancements since > Apache Commons JCS 3.0 was released, so I would like to release Apache > Commons JCS 3.1. > > [X] +1 Release t

[VOTE] Release Apache Commons JCS 3.1 based on rc2

hat 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, Thomas Vandahl (tv), Release Manager (using key 88817402) --

[CANCEL][VOTE] Release Apache Commons JCS 3.1 based on RC1

> Am 23.12.2021 um 19:20 schrieb Thomas Vandahl : > > Hi folks, > > We have fixed quite a few bugs and added some significant enhancements since > Apache Commons JCS 3.0 was released, so I would like to release Apache > Commons JCS 3.1. Thanks to Bruno we were able to fin

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

> Am 29.12.2021 um 16:06 schrieb Gary Gregory : > > Is this test failure being addressed? Well, "addressed" is a big word for what I'm currently trying. "looked at" is closer to what happens. Bye, Thomas - To unsubscribe,

Re: can we get rid of dependabot?

+1 Thank you, Phil. This thing is a P.I.T.A. > Am 28.12.2021 um 19:20 schrieb Phil Steitz : > > I can no longer effectively monitor commits@ due to the spam generated by > this tool. I am afraid my eyeballs aren't the only ones going missing here > and that is a problem much more severe than

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

> Am 28.12.2021 um 13:01 schrieb Bruno P. Kinoshita > : > > `mvn clean test install site` took a few minutes, but it just finished > running. Below the error that just happened again on my environment (appears > to be consistent for me): > > [INFO] Results: > [INFO] > [ERROR] Failures: >

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

Hi Bruno. > Am 24.12.2021 um 02:00 schrieb Bruno P. Kinoshita > : > > [ERROR] SerializerUnitTest.testReadWrite:116 [key:0] should not be null, > Region Name = blockRegion2 Can you reproduce the failure (because I can't)? Some of the concurrent tests are timing sensitive. If you can

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

My vote: > Am 23.12.2021 um 19:20 schrieb Thomas Vandahl : > > [X] +1 Release these artifacts > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this release becau

Re: [VOTE] Release Apache Commons JCS 3.1 based on RC1

Yeah, sorry - typo. > Am 23.12.2021 um 19:20 schrieb Thomas Vandahl : > > The Git tag commons-jcs3-3.1-rc1 commit for this RC is > f370adb43aeef51a5456d93f13f2601f3b87c44a which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-

[VOTE] Release Apache Commons JCS 3.1 based on RC1

/commons-jcs3-core/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 thi

Re: [commons-jcs] branch master updated: Use for-each. Use final. Remove redundant modifiers.

Hi Gary, On 21.11.20 19:22, ggreg...@apache.org wrote: This is an automated email from the ASF dual-hosted git repository. ggregory pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/commons-jcs.git The following commit(s) were added to refs/heads/master by

Re: [All] New repo for all proper components as submodules?

On 30.08.20 00:52, Gary Gregory wrote: Hi All, Any thoughts for or against creating a new git repository which would contain all 'proper' Commons components as git submodules? The idea is to be able to checkout all of Commons 'proper' in one go in one place. I understand this is in addition

[ANNOUNCE] Apache Commons JCS 3.0 Released

The Apache Commons Team is pleased to announce the availability of Apache Commons JCS 3.0 Apache Commons JCS is a distributed, versatile caching system. This has been a major overhaul of JCS with many adjustments for JDK 8+, better concurrency and logging. Commons JCS 3.0 requires Java 8 or

[RESULT] [VOTE] Release Apache Commons JCS 3.0 based on RC1

On 17.08.20 08:29, Thomas Vandahl wrote: > This has been a major overhaul of JCS with many adjustments for JDK 8+, > better concurrency and logging. Finally, I would like to > release Apache Commons JCS 3.0. More than 72 hours have now passed, and there have been the following votes

REMINDER: [VOTE] Release Apache Commons JCS 3.0 based on RC1

Could I please ask for one more PMC vote? TIA Bye, Thomas On 17.08.20 08:29, Thomas Vandahl wrote: > This has been a major overhaul of JCS with many adjustments for JDK 8+, > better concurrency and logging. Finally, I would like to > release Apache Commons JCS 3.0. [...] > P

Re: [VOTE] Release Apache Commons JCS 3.0 based on RC1

On 17.08.20 08:29, Thomas Vandahl wrote: > [X] +1 Release these artifacts > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this release because... Bye, Thomas - To unsubscribe,

[VOTE] Release Apache Commons JCS 3.0 based on RC1

This has been a major overhaul of JCS with many adjustments for JDK 8+, better concurrency and logging. Finally, I would like to release Apache Commons JCS 3.0. Apache Commons JCS 3.0 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/jcs/3.0-RC1 (svn revision

Re: [all] Thoughts on build system maven -> gradle??

On 17.07.20 10:13, Claude Warren wrote: > -1 from me. I have a philosophical objection. Same here: -1 > Much like HTTP's mod_rewrite[1] gradle's greatest strength is that it > allows the developer to do so much in so many ways. But its greatest > weakness is that it allows the developer to do

Re: [CONFIGURATION] Formatting braces

On 11.09.19 15:53, Gary Gregory wrote: > public static final ConfigurationConsumer > DEFAULT_INCLUDE_LISTENER = e -> { throw e; }; > > public static final ConfigurationConsumer > NOOP_INCLUDE_LISTENER = e -> { /* noop */ }; +1 for these. > I propose a reformatting to use the "{ on the

Re: svn commit: r1859859 [1/5] - in /commons/proper/jcs/trunk/commons-jcs-core/src: main/java/org/apache/commons/jcs/ main/java/org/apache/commons/jcs/access/ main/java/org/apache/commons/jcs/admin/ m

On 27.05.19 10:21, sebb wrote: > Either re-apply each of the commits in turn to Git. Done. Bye, Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: svn commit: r1859859 [1/5] - in /commons/proper/jcs/trunk/commons-jcs-core/src: main/java/org/apache/commons/jcs/ main/java/org/apache/commons/jcs/access/ main/java/org/apache/commons/jcs/admin/ m

On 26.05.19 15:54, sebb wrote: > Jan 2019 > > https://lists.apache.org/thread.html/053bb8f18e90800d918956f69364167b23c0cdca175568300b1108f6@%3Cdev.commons.apache.org%3E Ok, I missed that one completely. What do I have to do? Bye, Thomas

Re: svn commit: r1859859 [1/5] - in /commons/proper/jcs/trunk/commons-jcs-core/src: main/java/org/apache/commons/jcs/ main/java/org/apache/commons/jcs/access/ main/java/org/apache/commons/jcs/admin/ m

On 24.05.19 12:33, Gary Gregory wrote: > -1 > > We are now on gitbox https://gitbox.apache.org/repos/asf/commons-jcs.git > When did that happen? I don't remember an announcement or a vote. Bye, Thomas - To unsubscribe,

[csv] Integrate SuperCSV? was :Re: [VOTE] Release Apache Commons CSV 1.6 based on RC1

On 9/19/18 2:31 PM, Benedikt Ritter wrote: > we have fixed some bugs and added some features since Commons CSV 1.5 has > been released, so I would like to release Commons CSV 1.6 based on RC1 I like the concept of cell processors and the bean mapping of SuperCSV. The maintainers have been seeking

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 9/7/18 2:11 PM, sebb wrote: > If the tag contains files that are not in the distribution, why are > they present at all? Because they are experimental code, for example. Not ready for prime time. > If they are needed, why are they not in the distribution? They are not needed, at least not

[RESULT][VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 8/23/18 5:32 PM, Thomas Vandahl wrote: > I would like to make another attempt to release Apache Commons JCS 2.2.1 > (a bugfix release) > > Apache Commons JCS 2.2.1 RC4 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/jcs/ (svn revision 28918

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 27.08.18 18:12, Benedikt Ritter wrote: > ~/w/a/r/r/t/jcs git:(upstream ⚡ master) > diff -r commons-jcs-2.2.1-RC4/ > commons-jcs-2.2.1-src > Only in commons-jcs-2.2.1-RC4/: .gitignore > Only in commons-jcs-2.2.1-RC4/: .svn > Only in commons-jcs-2.2.1-RC4/: .travis.yml > Only in

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 23.08.18 17:32, Thomas Vandahl wrote: > I would like to make another attempt to release Apache Commons JCS 2.2.1 > (a bugfix release) > > Apache Commons JCS 2.2.1 RC4 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/jcs/ (svn revision 28918)

Re: [ALL] SHA256/512 hashes

On 30.08.18 13:45, sebb wrote: >> You are free to choose whatever developmentVersion should be recorded. > > It should not be necessary to downdate the new version. It isn't. You can configure that. > Huh? > > If a local workspace contains spurious files, by definition it is > inconsistent.

Re: [ALL] SHA256/512 hashes

On 31.08.18 10:46, Benedikt Ritter wrote: > Our release process is cumbersome and fragile leading to all release > looking a little different from each other, depending on who is RM. > The pain that our release process causes has been brought up again and > again since I started here at commons

Re: [ALL] SHA256/512 hashes

On 29.08.18 01:18, sebb wrote: >> It doesn't check out the tag into a separate directory to build the release >> artifacts? > > Last time I checked it did not. The release:perform goal does this and always did. See target/checkout. Bye, Thomas

Re: [ALL] SHA256/512 hashes

On 28.08.18 12:03, sebb wrote: > On 28 August 2018 at 09:25, Mark Struberg wrote: >>> This is unlikely to happen as long as it does not cover multi-module builds >> >> The maven-release-plugin covers multi-module releases since many years. >> >> In the projects I'm working on there is no 'release

Re: [ALL] SHA256/512 hashes

On 25.08.18 16:14, Gilles wrote: >>> Probably for those who don't want to use the release plugin :-) >> >> I was mainly following up on the thread about updating CP to AP 21 [1] >> >> But yes, it could be used as an alternative hashing method. > > I thought that the release plugin was intended

Re: New release distribution checksum policy

On 24.08.18 15:42, sebb wrote: > If it really is the case that the Apache Parent POM only creates the > checksums for artifacts with a specific name, then IMO it is badly > broken and needs a bug report. Feel free. Lines 425 to 454. > Note that it says: > "For every artifact distributed to the

Re: New release distribution checksum policy

Hi Benedikt, On 23.08.18 18:25, Benedikt Ritter wrote: > Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl : > >> Shall we use this for commons-parent? >> > > Sounds reasonable to me. If I'm not mistaken, the requirement for SHA-512 checksums only exists for

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 23.08.18 17:32, Thomas Vandahl wrote: > I would like to make another attempt to release Apache Commons JCS 2.2.1 > (a bugfix release) > > Apache Commons JCS 2.2.1 RC4 is available for review here: > [X] +1 Release these artifac

[VOTE] Release Apache Commons JCS 2.2.1 based on RC4

I would like to make another attempt to release Apache Commons JCS 2.2.1 (a bugfix release) Apache Commons JCS 2.2.1 RC4 is available for review here: https://dist.apache.org/repos/dist/dev/commons/jcs/ (svn revision 28918) The SVN tag commons-jcs-2.2.1-RC4 commit for this RC4 is here:

Fwd: New release distribution checksum policy

Shall we use this for commons-parent? Bye, Thomas. Forwarded Message Subject: Re: New release distribution checksum policy Date: Thu, 23 Aug 2018 08:02:45 +0200 From: Hervé BOUTEMY Reply-To: memb...@apache.org To: memb...@apache.org FYI, Apache parent POM 21 has been released

Re: [VOTE] Release Apache Commons Pool 2.6.1 based on RC1

On 17.08.18 18:07, Gary Gregory wrote: > These are the Maven artifacts and their hashes in Nexus: > > #Release SHA-256s > #Fri Aug 17 09:52:45 MDT 2018 > commons-pool2-2.6.1-bin-zip.asc=c557973fdb9b917eb9bd3aea01db5ec1fd9ba81dc44de3ebbfcf0d30d3034457 My understanding of the new release policy is

Re: [release-plugin] best multi-module project?

On 18.02.18 14:20, Rob Tompkins wrote: > Not quite because our release process isn’t precisely the same as what maven > does. Hence, our release plugin strives to be a shim for our site and > distribution files. But yes, I agree that “mvn deploy” should essentially do > everything you need.

Re: [release-plugin] best multi-module project?

On 07.02.18 00:28, Gilles wrote: > Having no idea on how to achieve it, I'd wish that creating > the "full dist" only requires a custom "goal" like (?) >  $ mvn package:dist > with no ad-hoc directory/module: all modules specified in the > top POM would have their artefacts (recursively) bundled

Re: [VOTE] Release Commons JCS 2.2.1 based on RC3

On 15.12.17 14:05, Romain Manni-Bucau wrote: > Here what I tested: > > 1. svn co > 2. mvn clean install > 3. mvn source:jar > > => the same trash is here > > 4. mvn clean source:jar > > => same happens > > so I guess something more fishy happens :( What is wrong with mvn

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

On 12.12.17 09:14, Romain Manni-Bucau wrote: > This is the part I really don't understand since it will never work. Yes, I know. And I agree. But it's the process in commons as of now. Let's get this out of the door and save the discussion for later. Please? Bye, Thomas

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

On 11.12.17 22:43, Romain Manni-Bucau wrote: > I can drop the rc2, no problem but can you confirm rc3 will be this exact > vote with revisions as only change? yes, and the RC-tag is probably required. Bye, Thomas. - To

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

Hi Romain, On 20.11.17 09:15, Romain Manni-Bucau wrote: > do we have a real blocker on the release? Being said having the RC or > not now is pointless since the tag is there, are we waiting for > anything particular? Happy to drop the RC if it brings more confusion > than it helps. Would you

Re: prevent registering JCSAdminBean multiple times

On 16.11.17 21:54, Tim Cronin wrote: > we have a few webapps running on the same server that use JCS. > > when moving the 2.x we started getting the following error on tomcat startup > > > > javax.management.InstanceAlreadyExistsException: It looks like you load multiple instances of

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

On 06.11.17 21:11, Romain Manni-Bucau wrote: > created > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC2/ > (rev 1814438) Thanks, Romain. However, the POM file in this RC tag contains now --8<--

  1   2   3   >