You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Steve Dodge (JIRA)" <ji...@codehaus.org> on 2008/08/26 00:18:26 UTC

[jira] Created: (MRM-924) Artifact information screen should indicate the origin of the artifact

Artifact information screen should indicate the origin of the artifact 
-----------------------------------------------------------------------

                 Key: MRM-924
                 URL: http://jira.codehaus.org/browse/MRM-924
             Project: Archiva
          Issue Type: Improvement
    Affects Versions: 1.1.2
            Reporter: Steve Dodge
            Priority: Minor


Looking at the artifact info screen, there is no information related to how the artifact got there.  It would be great if this information could be tracked and made visible e.g. by which proxy connector was this artifact pulled from or the username if manually deployed.

-- 
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

        

[jira] Updated: (MRM-924) Artifact information screen should indicate the origin of the artifact

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-924:
---------------------------------

    Fix Version/s: 1.x

> Artifact information screen should indicate the origin of the artifact 
> -----------------------------------------------------------------------
>
>                 Key: MRM-924
>                 URL: http://jira.codehaus.org/browse/MRM-924
>             Project: Archiva
>          Issue Type: Improvement
>    Affects Versions: 1.1.2
>            Reporter: Steve Dodge
>            Priority: Minor
>             Fix For: 1.x
>
>
> Looking at the artifact info screen, there is no information related to how the artifact got there.  It would be great if this information could be tracked and made visible e.g. by which proxy connector was this artifact pulled from or the username if manually deployed.

-- 
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

        

[jira] Commented: (MRM-924) Artifact information screen should indicate the origin of the artifact

Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145955#action_145955 ] 

Wendy Smoak commented on MRM-924:
---------------------------------

I'm not sure we currently store that information anywhere that would allow us to display it later, but the audit log should have it.

> Artifact information screen should indicate the origin of the artifact 
> -----------------------------------------------------------------------
>
>                 Key: MRM-924
>                 URL: http://jira.codehaus.org/browse/MRM-924
>             Project: Archiva
>          Issue Type: Improvement
>    Affects Versions: 1.1.2
>            Reporter: Steve Dodge
>            Priority: Minor
>
> Looking at the artifact info screen, there is no information related to how the artifact got there.  It would be great if this information could be tracked and made visible e.g. by which proxy connector was this artifact pulled from or the username if manually deployed.

-- 
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