As number of languages is increased, the time used to process them is bigger
every time you do a "mvn clean install". Thanks to this new profile you could
save some timpe passing the following argument "-P-i18n".
FEA: ItEr76S03Community
As number of languages is increased, the time used to process them is bigger
every time you do a "mvn clean install". Thanks to this new profile you could
save some timpe passing the following argument "-P-i18n".
FEA: ItEr76S03Community
The background position of the current day and deadline was outside the
visible area in the timetracker watermark columns when it was on the
last day of the interval.
A better alignment with the tasks layer (reducing the 3px max deviation)
on this cases can be achieved by revamping how lines and borders are
represented on the watermark layer.
FEA: ItEr76S04BugFixing
The background position of the current day and deadline was outside the
visible area in the timetracker watermark columns when it was on the
last day of the interval.
A better alignment with the tasks layer (reducing the 3px max deviation)
on this cases can be achieved by revamping how lines and borders are
represented on the watermark layer.
FEA: ItEr76S04BugFixing
doAfterCompose instead of constructor.
When doAfterCompose is run, we are sure we are ready to send messages to the
client side.
FEA: ItEr76S04BugFixing
doAfterCompose instead of constructor.
When doAfterCompose is run, we are sure we are ready to send messages to the
client side.
FEA: ItEr76S04BugFixing
When a task is potentially modified is not needed to change the start
and the end date. This was causing two invokations of the
"dependencies" algorithm. Now only one is done.
Although the constraint is not applied it must be provided. Otherwise
the dominating forces would not take it into account. Normally this
wasn't a problem since if the secondary point date changes it was
provided. But it can happen that the secondary point doesn't change,
in that case the constraint must still be taken into account.
When a task is potentially modified is not needed to change the start
and the end date. This was causing two invokations of the
"dependencies" algorithm. Now only one is done.
Although the constraint is not applied it must be provided. Otherwise
the dominating forces would not take it into account. Normally this
wasn't a problem since if the secondary point date changes it was
provided. But it can happen that the secondary point doesn't change,
in that case the constraint must still be taken into account.
The order in the deletion of the different objects related with the task was
wrong and it was causing an exception.
Moreover, the exception was breaking the flow of execution in our application
and preventing that the size of container was updated.
FEA: ItEr76S04BugFixing
The order in the deletion of the different objects related with the task was
wrong and it was causing an exception.
Moreover, the exception was breaking the flow of execution in our application
and preventing that the size of container was updated.
FEA: ItEr76S04BugFixing
Add French translation for main translation files (.pot) and report files
(.properties).
Translation mainly done by Philippe Poumaroux with contributions by Stephane
Ayache and Guillaume Postaire.
Add French translation for main translation files (.pot) and report files
(.properties).
Translation mainly done by Philippe Poumaroux with contributions by Stephane
Ayache and Guillaume Postaire.
