Re: [validator] broken test on my build but ok on GH

2024-12-25 Thread Gary Gregory
On Wed, Dec 25, 2024 at 7:56 PM Gary Gregory wrote: > For me, createCalendar() returns: > > > java.util.GregorianCalendar[time=113599170,areFieldsSet=true,areAllFieldsSet=false,lenient=true,zone=sun.util.calendar.ZoneInfo[id="GMT",offset=0,dstSavings=0,useDaylight=false,transitions=0,lastRule

Re: [validator] broken test on my build but ok on GH

2024-12-25 Thread Gary Gregory
For me, createCalendar() returns: java.util.GregorianCalendar[time=113599170,areFieldsSet=true,areAllFieldsSet=false,lenient=true,zone=sun.util.calendar.ZoneInfo[id="GMT",offset=0,dstSavings=0,useDaylight=false,transitions=0,lastRule=null],firstDayOfWeek=2,minimalDaysInFirstWeek=4,ERA=1,YEAR=2

Re: [validator] broken test on my build but ok on GH

2024-12-25 Thread Dávid Szigecsán
I don't know either. The created calendar `final Calendar cal20051231 = createCalendar(GMT, 20051231, 11500);` means it is 2005-12-31 01:15:00. I can't understand yet how could it be a day before (2005-12-30) in your case. Could it be the createCalendar() method, which generates the Calendar wrong

Re: [validator] broken test on my build but ok on GH

2024-12-25 Thread Gary Gregory
Hi Dávid, Thank you for having a look. I can't figure out why this is failing on my setup. Quite annoying since I can't build or consider creating a release candidate until this is addressed. Gary On Wed, Dec 25, 2024, 4:31 PM Dávid Szigecsán wrote: > Hi, > > I checked it on Java 23 and seeme

Re: [validator] broken test on my build but ok on GH

2024-12-25 Thread Dávid Szigecsán
Hi, I checked it on Java 23 and seemed fine. [INFO] Running org.apache.commons.validator.routines.CalendarValidatorTest [INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.104 s -- in org.apache.commons.validator.routines.CalendarValidatorTest Apache Maven 3.9.9 (8e8579a9e7

Re: [LAZY][VOTE] Release Apache Commons Skin 5.0.0 based on RC1

2024-12-25 Thread Gary Gregory
My +1 Gary On Wed, Dec 25, 2024, 2:36 PM Gary Gregory wrote: > To use more and more of the current Maven plugins, we must update > the Apache Commons Skin to Doxia 2. This release accomplishes that. > > Apache Commons Skin 5.0.0 RC1 does not have a Subversion staging directory > (for some reaso

[LAZY][VOTE] Release Apache Commons Skin 5.0.0 based on RC1

2024-12-25 Thread Gary Gregory
To use more and more of the current Maven plugins, we must update the Apache Commons Skin to Doxia 2. This release accomplishes that. Apache Commons Skin 5.0.0 RC1 does not have a Subversion staging directory (for some reason lost to the sands of time). The Git tag commons-skin-5.0.0-RC1 commit f

[validator] broken test on my build but ok on GH

2024-12-25 Thread Gary Gregory
Hi All, With the HEAD of git master (commit 2c1898f65ed46aa5c0f340f63b5e1f4a8b86e4f0), I get: [WARNING] Tests run: 25, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.007 s -- in org.apache.commons.validator.routines.EmailValidatorTest [INFO] Running org.apache.commons.validator.routines.Cale