Re: [VOTE] Release Apache Commons Configuration 2.11.0 based on RC1

Hi Gary, > Am 07.06.2024 um 15:53 schrieb Gary Gregory : > > We have fixed a few bugs and added enhancements since Apache Commons > Configuration 2.10.1 was released, so I would like to release Apache > Commons Configuration 2.11.0. > > Apache Commons Configuration 2.11.0 RC1 is available for

Re: Question on updating Turbine core

Hi Jeff, > Am 05.06.2024 um 20:32 schrieb Jeffery Painter : > > Hi Turbine devs, > > I setup a new Ubuntu 24.0 server the other day for some testing, and realized > my apps would not load since by default, they have switched the packages from > Tomcat 9.x to Tomcat 10.x. Should we plan to

[ANNOUNCE] Apache Commons JCS 3.2.1

://commons.apache.org/proper/commons-jcs/download_jcs.cgi Historical list of changes: https://commons.apache.org/proper/commons-jcs/changes-report.html Enjoy! Thomas Vandahl -Apache Commons JCS team

[jira] [Resolved] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration

[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl resolved JCS-235. Fix Version/s: jcs-3.2.1 Resolution: Cannot Reproduce > Thread leakage in JCS 3.1 with prim

[jira] [Resolved] (JCS-240) Remote cache appears incompatible with JDK 8u241 and above

[ https://issues.apache.org/jira/browse/JCS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl resolved JCS-240. Fix Version/s: jcs-3.2.1 Resolution: Fixed Fixed in release 3.2.1 > Remote cache appe

[ANNOUNCE] Apache Commons JCS 3.2.1

://commons.apache.org/proper/commons-jcs/download_jcs.cgi Historical list of changes: https://commons.apache.org/proper/commons-jcs/changes-report.html Enjoy! Thomas Vandahl -Apache Commons JCS team - To unsubscribe, e-mail: user-unsubscr

[ANNOUNCE] Apache Commons JCS 3.2.1

://commons.apache.org/proper/commons-jcs/download_jcs.cgi Historical list of changes: https://commons.apache.org/proper/commons-jcs/changes-report.html Enjoy! Thomas Vandahl -Apache Commons JCS team - To unsubscribe, e-mail: dev-unsubscr

[RESULT][VOTE] Release Apache Commons JCS 3.2.1 based on rc3

This vote thread passes with the following binding +1 votes: - Gary Gregory (ggregory) - Rob Tompkins (chtompki) - Thomas Vandahl (tv) I will proceed with the release process. Thanks to the voters. Bye, Thomas > Am 27.05.2024 um 20:24 schrieb Thomas Vandahl : > > Hi folks, > >

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

My vote > Am 27.05.2024 um 20:24 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 rc3 is available for review here: >

[VOTE] Release Apache Commons JCS 3.2.1 based on rc3

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 rc3 is available for review here: https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc3 (svn revision 69406) The Git tag

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

Next attempt. > 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

Re: [VOTE] RC Torque 6.0 based on staged repository

> Am 08.05.2024 um 15:54 schrieb Kallidis, Georg : > > Hi Torque community, > > a release candidate for Torque version 6.0 has been prepared (closed in > nexus.apache.org) and is open for voting! > > [X] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because

[JCS] How to proceed? was: Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc2

at a loss on how to tackle this problem. I'm open for suggestions. Please help! Bye, Thomas > Am 05.05.2024 um 19:20 schrieb Thomas Vandahl : > > Hi Bruno, > >> Am 02.05.2024 um 22:01 schrieb Bruno Kinoshita : >> >> Tried building the project but alas I thin

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

Hi Bruno, > Am 02.05.2024 um 22:01 schrieb Bruno Kinoshita : > > Tried building the project but alas I think my network has UDP multicast > issues? > > [ERROR] Failures: > [ERROR] UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:122 > message not received > [ERROR]

Re: [VOTE] Maven archetype for Turbine 6.0

Hi Jeff, > Am 23.04.2024 um 21:45 schrieb Jeffery Painter : > > Hello turbine devs, > > After some frustration, I finally got my credentials all sorted out and I > think I have successfully staged a release candidate for the maven archetype. > > Tag: turbine-webapp-6.0-3.0.0 > > Git repo:

Re: svn commit: r1917286 - /turbine/fulcrum/trunk/KEYS

Hi Jeff, > Am 24.04.2024 um 14:34 schrieb Jeffery Painter : > > https://downloads.apache.org/turbine/KEYS > > I'm not sure where that file lives and how to update it. > My guess is https://dist.apache.org/repos/dist/release/turbine/KEYS Bye, Thomas

Re: [VOTE] Release Apache Commons CSV 1.11.0 based on RC1

Hi Gary, > Am 29.04.2024 um 00:24 schrieb Gary Gregory : > > We have fixed a few bugs and added enhancements (better Microsoft > Excel compatibility) since Apache Commons CSV 1.10.0 was released, so > I would like to release Apache Commons CSV 1.11.0. > > [X] +1 Release these artifacts > [ ]

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

Hi folks, > 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: >

Re: Preparing Release Torque 5.2 / 6.0

Hi Georg, > Am 05.04.2024 um 14:41 schrieb Kallidis, Georg : > > I think we should release as version 6.0 as this might be enough clear that > we break support for Java 8? If you don't mind I'd try to eliminate all deprecated code. Bye, Thomas

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: Preparing Release Torque 5.2 / 6.0

Hi Georg > Am 05.04.2024 um 14:41 schrieb Kallidis, Georg : > > Hi all Torque Devs, > > I am in the process to prepare a Torque release, currently as version 5.2. > > Except changes in the code like fixes and features, this release will support > only Java 11. > > I think we should release

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 Candidate Turbine Core v6.0

Hi Georg, > Am 26.01.2024 um 10:47 schrieb Kallidis, Georg : > > another new Turbine Core version 6.0 release candidate has been prepared! > ... > [X] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because > Signatures look ok. Build is ok using Apache Maven

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

[jira] [Comment Edited] (JCS-240) Remote cache appears incompatible with JDK 8u241 and above

[ https://issues.apache.org/jira/browse/JCS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782280#comment-17782280 ] Thomas Vandahl edited comment on JCS-240 at 11/4/23 5:15 PM: - See https

[jira] [Commented] (JCS-240) Remote cache appears incompatible with JDK 8u241 and above

[ https://issues.apache.org/jira/browse/JCS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782909#comment-17782909 ] Thomas Vandahl commented on JCS-240: I'm planning to release this as a patch release 3.2.1 because I

[jira] [Commented] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration

[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782321#comment-17782321 ] Thomas Vandahl commented on JCS-235: [~Amol D]: Any news? Did the workaround help? > Thread leak

[jira] [Commented] (JCS-236) Request support for JDK17/Jakarta in JCS3.1

[ https://issues.apache.org/jira/browse/JCS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782320#comment-17782320 ] Thomas Vandahl commented on JCS-236: At the current time, there is no plan for this. > Request supp

[jira] [Resolved] (JCS-236) Request support for JDK17/Jakarta in JCS3.1

[ https://issues.apache.org/jira/browse/JCS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl resolved JCS-236. Assignee: Thomas Vandahl Resolution: Won't Fix > Request support for JDK17/Jakarta in JCS

[jira] [Resolved] (JCS-238) Every update to JCS Remote Cache update takes nearly ~2 seconds

[ https://issues.apache.org/jira/browse/JCS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl resolved JCS-238. Fix Version/s: (was: jcs-3.1) Assignee: Thomas Vandahl Resolution: Duplicate Work

[jira] [Resolved] (JCS-239) CacheAccess put/remove in one application is not getting reflected in another application

[ https://issues.apache.org/jira/browse/JCS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl resolved JCS-239. Assignee: Thomas Vandahl Resolution: Duplicate Work will be done in JCS-240 > CacheAccess

[jira] [Resolved] (JCS-237) Remote Cache update makes lot of log entries

[ https://issues.apache.org/jira/browse/JCS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl resolved JCS-237. Fix Version/s: (was: jcs-3.1) Assignee: Thomas Vandahl Resolution: Duplicate Work

[jira] [Updated] (JCS-240) Remote cache appears incompatible with JDK 8u241 and above

[ https://issues.apache.org/jira/browse/JCS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-240: --- Assignee: Thomas Vandahl > Remote cache appears incompatible with JDK 8u241 and ab

[jira] [Commented] (JCS-240) Remote cache appears incompatible with JDK 8u241 and above

[ https://issues.apache.org/jira/browse/JCS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782314#comment-17782314 ] Thomas Vandahl commented on JCS-240: Would you please try branch [release-3.2.1|https://github.com

Re: [VOTE] Release (second RC) fulcrum-security v3.0.0 based on staged repository

Hi Georg, > Am 23.10.2023 um 14:31 schrieb Georg Kallidis > : > > Hi Turbine devs, > > after the first a second candidate was prepared for sub module Fulcrum > Security having version 3.0.0. > > [X] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because

[jira] [Updated] (JCS-240) Remote cache appears incompatible with JDK 8u241 and above

[ https://issues.apache.org/jira/browse/JCS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-240: --- Summary: Remote cache appears incompatible with JDK 8u241 and above (was: Remote cache appears

[jira] [Commented] (JCS-240) Remote cache appears incompatible with JDK 11+

[ https://issues.apache.org/jira/browse/JCS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782280#comment-17782280 ] Thomas Vandahl commented on JCS-240: See https://bugs.openjdk.org/browse/JDK-8237213 for an explanation

[jira] [Commented] (JCS-240) Remote cache appears incompatible with JDK 11+

[ https://issues.apache.org/jira/browse/JCS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782256#comment-17782256 ] Thomas Vandahl commented on JCS-240: Hi Greg, thank you for spotting this. I need to have a closer look

[jira] [Commented] (JCS-238) Every update to JCS Remote Cache update takes nearly ~2 seconds

[ https://issues.apache.org/jira/browse/JCS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776584#comment-17776584 ] Thomas Vandahl commented on JCS-238: There are lots of examples in the [docs|https://commons.apache.org

Re: [VOTE] Release fulcrum-security v3.0.0. based on staged repository

Hi Georg, > Am 12.10.2023 um 17:42 schrieb Georg Kallidis > : > > Hi Turbine devs, > > a new release candidate was prepared for sub module Fulcrum Security > having version 3.0.0. > > [X] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because Signatures are ok,

[jira] [Commented] (JCS-238) Every update to JCS Remote Cache update takes nearly ~2 seconds

[ https://issues.apache.org/jira/browse/JCS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774566#comment-17774566 ] Thomas Vandahl commented on JCS-238: First, you have configured ElementAttributes in cache-client.ccf

[jira] [Updated] (JCS-238) Every update to JCS Remote Cache update takes nearly ~2 seconds

[ https://issues.apache.org/jira/browse/JCS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-238: --- Priority: Minor (was: Major) > Every update to JCS Remote Cache update takes nearly ~2 seco

[jira] [Updated] (JCS-238) Every update to JCS Remote Cache update takes nearly ~2 seconds

[ https://issues.apache.org/jira/browse/JCS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-238: --- Issue Type: Question (was: Bug) > Every update to JCS Remote Cache update takes nearly ~2 seco

[jira] [Comment Edited] (JCS-238) Every update to JCS Remote Cache update takes nearly ~2 seconds

[ https://issues.apache.org/jira/browse/JCS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774367#comment-17774367 ] Thomas Vandahl edited comment on JCS-238 at 10/12/23 8:16 AM: -- Is there any

Re: [VOTE] Release fulcrum-parser v3.0.0. based on staged repository

Hi Georg, > Am 26.09.2023 um 17:22 schrieb Georg Kallidis > : > > Hi Turbine devs, > > again - another new Turbine release candidate has been prepared version, > Fulcrum Parser 3.0.0. > > [X] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because My vote. Bye,

[jira] [Commented] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration

[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767179#comment-17767179 ] Thomas Vandahl commented on JCS-235: The thread dump looks strange. Obviously, you have multiple threads

[jira] [Comment Edited] (JCS-237) Remote Cache update makes lot of log entries

[ https://issues.apache.org/jira/browse/JCS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767143#comment-17767143 ] Thomas Vandahl edited comment on JCS-237 at 9/20/23 2:43 PM: - The error message

[jira] [Commented] (JCS-238) Every update to JCS Remote Cache update takes nearly ~2 seconds

[ https://issues.apache.org/jira/browse/JCS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767147#comment-17767147 ] Thomas Vandahl commented on JCS-238: I don't see anything obvious in the configuration. I'd suggest

[jira] [Commented] (JCS-237) Remote Cache update makes lot of log entries

[ https://issues.apache.org/jira/browse/JCS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767143#comment-17767143 ] Thomas Vandahl commented on JCS-237: The error message suggests that you have a cache listener

[jira] [Comment Edited] (JCS-237) Remote Cache update makes lot of log entries

[ https://issues.apache.org/jira/browse/JCS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767143#comment-17767143 ] Thomas Vandahl edited comment on JCS-237 at 9/20/23 2:45 PM: - The error message

[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

[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: user

[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

[jira] [Updated] (JCS-233) 3.2 Release Date?

[ https://issues.apache.org/jira/browse/JCS-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-233: --- Fix Version/s: jcs-3.2 > 3.2 Release Date? > - > >

[jira] [Resolved] (JCS-233) 3.2 Release Date?

[ https://issues.apache.org/jira/browse/JCS-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl resolved JCS-233. Resolution: Fixed JCS 3.2 released > 3.2 Release Date? > - > >

[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 (

[jira] [Commented] (JCS-236) Request support for JDK17/Jakarta in JCS3.1

[ https://issues.apache.org/jira/browse/JCS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761617#comment-17761617 ] Thomas Vandahl commented on JCS-236: One comment in addition to Garys (correct) statement: The said

[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

[jira] [Commented] (JCS-236) Request support for JDK17/Jakarta in JCS3.1

[ https://issues.apache.org/jira/browse/JCS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757497#comment-17757497 ] Thomas Vandahl commented on JCS-236: Can you please provide more details as to what is incompatible

[jira] [Commented] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration

[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757496#comment-17757496 ] Thomas Vandahl commented on JCS-235: Could you please provide a log file showing the behaviour? Please

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

Re: [VOTE] Release fulcrum-testcontainer 2.0.0 based on staged repository

> Am 15.08.2023 um 09:41 schrieb Georg Kallidis > : > > Hi Turbine devs, > > a new Turbine Fulcrum Testcontainer release candidate has been prepared. ... > Reply by checking one: > > [X] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because Signatures are ok,

[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] Release fulcrum-yaafi 2.0.0 based on staged repository

> Am 19.07.2023 um 13:38 schrieb Georg Kallidis > : > > Reply by checking one: > > [X] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because > Signatures are ok, build and tests run fine with —8<— Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)

Re: Antwort: Re: [VOTE] Release fulcrum-intake 3.0.0 based on staged repository

Hi Georg, > Am 12.06.2023 um 08:33 schrieb Georg Kallidis > : > > It's just the version number i changed, because we are not backward > comaptible now, with Java 11 baseline (before it was Java 8). > > Might be a good idea to do this for all upcoming Fulcrum releases .. > +1 > And if

Re: [VOTE] Release fulcrum-intake 3.0.0 based on staged repository

Hi Georg, > Am 09.06.2023 um 10:27 schrieb Georg Kallidis > : > > Reply by checking one: > > [X] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because Signatures and tests of source package ok. Environment —8<— Apache Maven 3.8.1

Re: [VOTE] Release turbine-parent v12 based on staged repository

Hi Georg, > Am 02.05.2023 um 11:44 schrieb Georg Kallidis > : > > Hi Turbine devs, > > a new Turbine Parent POM release candidate has been prepared: version 12. > > Tag: turbine-parent-12-candidate > > [X] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because >

[jira] [Resolved] (JCS-234) Imported packages for OSGi manifest incorrect

[ https://issues.apache.org/jira/browse/JCS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl resolved JCS-234. Fix Version/s: jcs-3.2 Resolution: Fixed Thanks for the patch. Fixed in Git. > Impor

[jira] [Updated] (JCS-234) Imported packages for OSGi manifest incorrect

[ https://issues.apache.org/jira/browse/JCS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-234: --- Assignee: Thomas Vandahl > Imported packages for OSGi manifest incorr

  1   2   3   4   5   6   7   8   9   10   >