You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Edwin Punzalan (JIRA)" <ji...@codehaus.org> on 2006/03/07 11:18:23 UTC

[jira] Commented: (MPIR-30) The automatically generated documentation should identify the project's group id, artifact id, and maybe version

    [ http://jira.codehaus.org/browse/MPIR-30?page=comments#action_60331 ] 

Edwin Punzalan commented on MPIR-30:
------------------------------------

Btw, I created a new goal "summary" which means there is another report page for this, as brett suggested.

The report page shows the following:
- general project information like project name, homepage.
- project organization
- build information like groupId, artifactId, version, and type

> The automatically generated documentation should identify the project's group id, artifact id, and maybe version
> ----------------------------------------------------------------------------------------------------------------
>
>          Key: MPIR-30
>          URL: http://jira.codehaus.org/browse/MPIR-30
>      Project: Maven 2.x Project Info Reports Plugin
>         Type: Improvement

>     Reporter: Howard M. Lewis Ship
>     Assignee: Edwin Punzalan
>      Fix For: 2.0

>
>
> The standard set of reports, i.e.,     ${reports}, should automatically generate  documentation identitying the group id and artifact id, as this is critical to making use of a maven project as a dependency. Perhaps this could go on the dependencies page.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org