|
The problem with
Patch applied,
kernel maven repo updated Thanks New patch applied.
thanks Probably wont get a snapshot out till tomorrow, takes to long on the link I am on. Could someone move this task and set the appropriate Fix version. I can't do that because it's a contributed patch.
Don't have JIRA permissions to reopen this, but it needs fixes. See comments in
please check and close, I should not have closed (request from Stephen Marquard)
Reopening for some changes as per
Changing to blocker to ensure this is addressed for 1.0.1 K1 for 2-6-x.
Patch that does the following:
1) Use 'available' & 'write' for resource (not dropbox) functions. Removed 'add' since an 'add' event shouldn't trigger an email. 2) Updated postAvailableEvent to delay an event if the resource isn't available. If the resource is available, check its properties to see if an 'available' event has been sent before, and if not send one then mark as 'availableNotified'. 3) Adjust priority of event to 'NOTI_NONE' in commitResourceEdit if resource is not yet available. This keeps 'write' events from sending an email each time an unavailable resource is updated. Almost done except getting duplicate notifications when revising a resource after it's available.
Resolved in trunk and 1.0.x. See
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Task
Resolved
Blocker
Create Delayable Events
Once 2.6 is out then we can look at this again.