of the CalendarExceptionType Entity.
It is caught in the validator. Otherwise it would be wraped by hibernate and would
bypass the automatic handling of OptimisttcLockingFailureExceptions
FEA: ItEr74S04BugFixing
A comment in the javadoc is added stating it. Final keyword is added
to the class so the immutability is not bypassed using
subclasses. Final cannot be applied to the fields because it must have
an empty constructor for Hibernate.
FEA: ItEr74S04BugFixing
The new date is equal to the new finish of task more one day.
So that the end date is not included in the reassigning of hours.
FEA: ItEr74S04BugFixing
Now the proportion is calculated differently for the consolidated values
and according to the percentage of the consolidation to which it belongs.
FEA: ItEr74S04BugFixing
of the CalendarExceptionType Entity.
It is caught in the validator. Otherwise it would be wraped by hibernate and would
bypass the automatic handling of OptimisttcLockingFailureExceptions
FEA: ItEr74S04BugFixing
of the orderElementTemplate Entity.
It is caught in the validator. Otherwise it would be wraped by hibernate and would
bypass the automatic handling of OptimisttcLockingFailureExceptions
FEA: ItEr74S04BugFixing
method of the workReportType entity.
It is caught in the validator. Otherwise it would be wraped by hibernate and would
bypass the automatic handling of OptimisttcLockingFailureExceptions
FEA: ItEr74S04BugFixing
* Changed constraintDate attribute in class TaskPositionConstraint to
IntraDayDate.
* Made all modifications needed to get this change working.
FEA: ItEr74S04BugFixing
This stretch is never added to the list of stretches, that means, it
won't be saved. On the contrary, is inferred from the endDate of the task.
FEA: ItEr74S04BugFixing
* The dayPoints and hoursPoints are calculated since the beginning of
the task.
* startInclusive is the first day with non-consolidated days.
* The function is only applied from (startInclusive, endExclusive).
* First, an allocation is done on the defined interval. Then the
remaining hours not used are calculated and the function is
applied again.
* Used function onInterval(start, end) for doing allocation instead of
iterating day by day.
FEA: ItEr74S04BugFixing
* Added test that causes the problem
* Fixed first issue as CHILDREN indirect advance was added before a
direct advance, and then always appear as spread.
* Fixed problem detected in the bug itself, updating spread advance when
some advance is removed.
FEA: ItEr74S07WBSTreeRefactoring
At limiting allocation when setting the day assignments, it used the
previous task's start and end date values instead of the ones just
calculated.
FEA: ItEr74S04BugFixing
