2 Commits (7cd45c2186e93a5b5eb26b006df9a4a0c882b32c)

Author	SHA1	Message	Date
ulferts	c5a968ec4c	place the registered project activities where they will not be unloaded (#4407) ... The config/ path is not registered in the autoload_path. Hence, putting values in variables placed there, will survive the constant reloading in the dev environment	9 years ago
ulferts	7e9dc28b55	place the registered project activities where they will not be unloaded (#4407) ... The config/ path is not registered in the autoload_path. Hence, putting values in variables placed there, will survive the constant reloading in the dev environment	9 years ago
ulferts	eae5321c4e	Feature/latest project activity (#4390) ... The project table is extended to also have the "Latest activity at" column which shows the date of the latest write operation within the project. https://community.openproject.com/work_packages/22858 Models can register for being considered when the latests activity date is calculated. This mechanism can be and is used by core and can also be used by plugins. It is unfortunate, that the mechanisms already in place by acts_as_activity could not be reused, but it would have required a complete rework to make it happen. Another shortcoming of the current implementation are the sql strings generated within Project::Activity. It would have taken more time to rework them into Arel and as the improvable code is limited to one class and a clean interface separates it from the rest of the application I deem it ok to stay that way for now.	9 years ago