Dan, there's a more fundamental problem here, which has blocked my progress. What you refer to is probably the individual artifact atom feed, which contains the entry/source/updated value. It also contains another value at entry/updated, which always remains the same and is actually the created time.
Now, for a workspace feed there's no source child node, and the one at entry/updated is not correct. My proposal is to at least make the entry/updated timestamp reflect what entry/source/updated contains.
Andrew Perepelytsya added a comment - 15/Feb/08 11:16 AM Dan, there's a more fundamental problem here, which has blocked my progress. What you refer to is probably the individual artifact atom feed, which contains the entry/source/updated value. It also contains another value at entry/updated, which always remains the same and is actually the created time.
Now, for a workspace feed there's no source child node, and the one at entry/updated is not correct. My proposal is to at least make the entry/updated timestamp reflect what entry/source/updated contains.
Dan Diephouse added a comment - 15/Feb/08 03:12 PM By critical do you mean I need to fix this before beta-2 next week? Or just that you can't add more features to the mule/galaxy distro?
Bug
Closed
Critical
Atom Last Update time isn't correct
Now, for a workspace feed there's no source child node, and the one at entry/updated is not correct. My proposal is to at least make the entry/updated timestamp reflect what entry/source/updated contains.