Building jBPM Console NG - Human Tasks Backend 6.1.0-SNAPSHOT Exception about jbpm-wb HOT 12 CLOSED

have you modified the tests in any way? and what is the time zone you're in as that might be specific to timezone?

from jbpm-wb.

Do you have any local changes?
It is working locally, so it might be related with your local environment. There is no way to fix if we don't find the cause..
@maciej is it failing in your local env?

from jbpm-wb.

@salaboy nope, works as expected, I even tried with the same date that is mentioned in the stack trace but still no luck to reproduce the problem.

from jbpm-wb.

If I remember correctly this issue is related to particular timezone(s) (as Maciej pointed out). I think @porcelli seen same (similar) issue some time ago. I will look into it (as I wrote the tests originally) once I have a minute or two.

from jbpm-wb.

No changes at all, I just get a fresh copy from Git every time to test and then remove all folders
about timezone

date +%Z
IRST
date +%z
+0330

I can build master branch with this command without any error
mvn clean install -DskipTests

from jbpm-wb.

@psiroky thanks I will appreciate if you take a look on those tests

from jbpm-wb.

The issue can be reproduced by adding following line at the start of method testGetTasksForLongPeriod().

DateTimeZone.setDefault(DateTimeZone.forTimeZone(TimeZone.getTimeZone("Brazil/East")));

It is related to the daylight savings time which is handled differently in different countries. I will look at how to fix the tests/implementation.

from jbpm-wb.

I just changed my timezone to Vancouver/Canada and problem solved.

sudo dpkg-reconfigure tzdata

Thanks for help.

from jbpm-wb.

alright the fix is to replace LocalDate.toDateMidnight() with LocalDate.toDateTimeAtStartOfDay() inside TaskServiceEntryPointImpl.transformLocalDatesToDays and that solves the problem. Any thoughts? If no objections I'll create jira and push it to master.

from jbpm-wb.

@mswiderski thanks for looking into this! Yes, the LocalDate.toDateTimeAtStartOfDay() is the right way to handle it. I am sorry for the inconvenience I caused, that method should have been used from the beginning.

from jbpm-wb.

@psiroky no worries, thanks for confirming the fix, I'll push that in.

from jbpm-wb.

fixed as part of this jira: https://issues.jboss.org/browse/JBPM-4226

from jbpm-wb.