[
http://jira.codehaus.org/browse/MRM-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111363
]
Wendy Smoak commented on MRM-564:
---------------------------------
>From IRC:
joakim: wsmoak_, re MRM-564 (audit.log) - go ahead and deploy a few things on
your copy of archiva/trunk (releases / snapshots / etc) and check out the
message text.
wsmoak_: where in the code? it will be a lot faster :)
joakim: is there anything missing in the text that you think should be there?
is there anything in the text that is too noisy?
joakim: AuditLog.java in archiva-webapp
wsmoak_: the next needs to say: who, what (artifact) where (repo? path?) and
when
joakim: ok, that's a useful sentance. add it to that jira.
I'm not likely to have time to set up a test for this, but I can review it if
you attach a log file.
I don't see anything in the AuditLog.java code that looks like it logs the user
who performed the action.
> Audit log is not populated when artifacts are deployed
> ------------------------------------------------------
>
> Key: MRM-564
> URL: http://jira.codehaus.org/browse/MRM-564
> Project: Archiva
> Issue Type: Improvement
> Components: Users/Security
> Affects Versions: 1.0-beta-3
> Reporter: Wendy Smoak
> Assignee: Joakim Erdfelt
> Fix For: 1.0-beta-4
>
>
> The audit.log file should contain an entry when any of the following events
> occurs: create directory, remove directory, create file, modify file, remove
> file.
> After a release, the audit.log file only contained:
> 2007-09-13 19:27:55 - Logging Initialized.
> There are no other audit log files. (I would have expected to see some with
> dates in the filename, the others are configured to roll on a daily basis.)
> (Needs to be verified with 1.0-beta-3 or later.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
