[VOTE] Release Apache Commons Configuration 2.11.1 based on RC1

2025-04-16 Thread Rob Tompkins
Hello all We have fixed a few bugs and added enhancements since Apache Commons Configuration 2.11.0 was released, so I would like to release Apache Commons Configuration 2.11.1. Apache Commons Configuration 2.11.1 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/comm

Re: [VFS] Should relative name be decoded

2025-04-16 Thread Bernd Eckenfels
Need to correct myself a bit: the change which prompted for my initial mail is not about escaping blanks in getPath(), getPath() (Depending on the provider) only escapes % (and ? and !). So the missing decode Variant of getRelativeName is limited to those. The escaped blanks happen in getURL an

Re: [RDF] Problems building master

2025-04-16 Thread Gary Gregory
Hi Fredy, GitHub shows builds are green on Java 11 and 17: https://github.com/apache/commons-rdf/actions Some unit tests are failing on Java 21 and up. Java 8 is no longer supported in git master (see the POM compiler settings). HTH, Gary On Wed, Apr 16, 2025 at 1:50 PM Fred Hauschel wrote: >

[RDF] Problems building master

2025-04-16 Thread Fred Hauschel
Hi there, haven't heard from me for a long time. I'm trying to think my way back into commons-rdf. I made a copy years ago that I'm building on, it's time to change that and switch to the original version. I just built the tag 0.5.0 successfully. but when I build master, I get an error. Used

Re: [VFS] Should relative name be decoded

2025-04-16 Thread Gary Gregory
Yeah, this needs more research IMO. One things I am sure of is that a global setting is a no-go for me as it is bound to cause problems in larger apps that may want conflicting values. Gary On Wed, Apr 16, 2025, 12:48 Bernd Eckenfels wrote: > > I think the encoding caused a lot of confusion wi

Re: [VFS] Should relative name be decoded

2025-04-16 Thread Bernd Eckenfels
I think the encoding caused a lot of confusion with people (and also I dont see how it is user friendly - besides if the calling Convention required it), but I dont think we can change that now. So I agree with Review and documenting. Maybe we need to provide at least a UriParser.decode() publ

Re: [VFS] Should relative name be decoded

2025-04-16 Thread Gary Gregory
Hi all, We probably need a general review of the API to see if we have an overall consistency issue RE encoded vs decoded. I prefer us to be considerate before adding APIs here and there. We could at least document what is expected for methods that return a String or consume a String. I wonder

[ANNOUNCE] Apache Commons JEXL Version 3.5.0

2025-04-16 Thread Gary Gregory
The Apache Commons team is pleased to announce Apache Commons JEXL Version 3.5.0. JEXL is a library intended to facilitate the implementation of dynamic and scripting features in applications and frameworks written in Java. JEXL implements an Expression Language based on some extensions to the JS

Re: [VOTE] Release Apache Commons JXPath 1.4.0 based on RC2

2025-04-16 Thread Gary Gregory
My +1 Gary On Sun, Apr 13, 2025 at 7:04 PM Gary Gregory wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > JXPath 1.3 was released, so I would like to release Apache Commons > JXPath 1.4.0. > > Apache Commons JXPath 1.4.0 RC2 is available for review here: > htt

[RESULT][VOTE] Release Apache Commons JEXL 3.5.0 based on RC2

2025-04-16 Thread Gary Gregory
This VOTE passes with the following binding +1 votes: - Henri Biestro (henrib) - Piotr P. Karwasz (ppkarwasz) - Gary Gregory (ggregory) TY all, Gary On Sat, Apr 12, 2025 at 1:59 PM Gary Gregory wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > JEXL 3.4.0 was rele

Re: [VOTE] Release Apache Commons JEXL 3.5.0 based on RC2

2025-04-16 Thread Gary Gregory
My +1 Gary On Sat, Apr 12, 2025 at 1:59 PM Gary Gregory wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > JEXL 3.4.0 was released, so I would like to release Apache Commons > JEXL 3.5.0. > > Apache Commons JEXL 3.5.0 RC2 is available for review here: > https:/