You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tim Pizey (JIRA)" <ji...@codehaus.org> on 2007/02/28 13:41:43 UTC
[jira] Created: (MSITE-214) Show repositories an artifact is
deployed to as a report
Show repositories an artifact is deployed to as a report
--------------------------------------------------------
Key: MSITE-214
URL: http://jira.codehaus.org/browse/MSITE-214
Project: Maven 2.x Site Plugin
Issue Type: Improvement
Affects Versions: 2.0-beta-5
Environment: All
Reporter: Tim Pizey
Google can get one to the website for an artifact, but discovering which repository it is deployed to seems to rely upon asking on IRC,
extracting the target repositories and creating a standard report would fix this.
--
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] Closed: (MPIR-87) Show repositories an artifact is deployed
to as a report
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MPIR-87.
-------------------------------
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.1
You could call mvn project-info-reports:dependencies
By default dependencyLocationsEnabled is set to true
> Show repositories an artifact is deployed to as a report
> --------------------------------------------------------
>
> Key: MPIR-87
> URL: http://jira.codehaus.org/browse/MPIR-87
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Environment: All
> Reporter: Tim Pizey
> Assignee: Vincent Siveton
> Fix For: 2.1
>
>
> Google can get one to the website for an artifact, but discovering which repository it is deployed to seems to rely upon asking on IRC,
> extracting the target repositories and creating a standard report would fix this.
--
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] Moved: (MPIR-87) Show repositories an artifact is deployed
to as a report
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg moved MSITE-214 to MPIR-87:
-------------------------------------------
Affects Version/s: (was: 2.0-beta-5)
Key: MPIR-87 (was: MSITE-214)
Project: Maven 2.x Project Info Reports Plugin (was: Maven 2.x Site Plugin)
> Show repositories an artifact is deployed to as a report
> --------------------------------------------------------
>
> Key: MPIR-87
> URL: http://jira.codehaus.org/browse/MPIR-87
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Environment: All
> Reporter: Tim Pizey
>
> Google can get one to the website for an artifact, but discovering which repository it is deployed to seems to rely upon asking on IRC,
> extracting the target repositories and creating a standard report would fix this.
--
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