You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org> on 2007/11/08 19:49:35 UTC
[jira] Closed: (MRM-564) Audit log is not populated when artifacts
are deployed
[ http://jira.codehaus.org/browse/MRM-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joakim Erdfelt closed MRM-564.
------------------------------
Resolution: Fixed
Closing this jira as fixed, as it only mentions logging Deployed content.
If we decide to log other content (see Mailing List) then we will open a new jira for that content.
Thread: http://www.nabble.com/-DISCUSS---MRM-564--Audit-Logging.-tf4772818.html
> 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