You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "William Ferguson (JIRA)" <ji...@codehaus.org> on 2010/06/03 01:20:12 UTC
[jira] Created: (MSITE-485) Add a DateBuilt field to the Build
Information section of the Project Summary page
Add a DateBuilt field to the Build Information section of the Project Summary page
----------------------------------------------------------------------------------
Key: MSITE-485
URL: http://jira.codehaus.org/browse/MSITE-485
Project: Maven 2.x Site Plugin
Issue Type: Improvement
Affects Versions: 2.1
Reporter: William Ferguson
One of the biggest problems (IMHO) when looking at project documentation is the inability to readily determine the age of a component or the age age of the documentation. Such information is often sued to make a decision on how relevant a new component might be.
The Project Summary page generated by the Site plugin contains a Build Information section.
This section identifies the GroupId, ArtifactId, Version, and Type.
If it also published the DateTime at which a component was built then it solve the problem above.
--
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-196) Add a DateBuilt field to the Build
Information section of the Project Summary page
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl moved MSITE-485 to MPIR-196:
------------------------------------------
Affects Version/s: (was: 2.1)
2.2
Key: MPIR-196 (was: MSITE-485)
Project: Maven 2.x Project Info Reports Plugin (was: Maven 2.x Site Plugin)
> Add a DateBuilt field to the Build Information section of the Project Summary page
> ----------------------------------------------------------------------------------
>
> Key: MPIR-196
> URL: http://jira.codehaus.org/browse/MPIR-196
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Affects Versions: 2.2
> Reporter: William Ferguson
>
> One of the biggest problems (IMHO) when looking at project documentation is the inability to readily determine the age of a component or the age age of the documentation. Such information is often sued to make a decision on how relevant a new component might be.
> The Project Summary page generated by the Site plugin contains a Build Information section.
> This section identifies the GroupId, ArtifactId, Version, and Type.
> If it also published the DateTime at which a component was built then it solve the problem above.
--
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-196) Add a DateBuilt field to the Build
Information section of the Project Summary page
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MPIR-196.
--------------------------------
Resolution: Won't Fix
The date is display using the site plugin (see the Last Published info), yes we could duplicate this information in the summary report but I don't think it is a necessary requirement.
> Add a DateBuilt field to the Build Information section of the Project Summary page
> ----------------------------------------------------------------------------------
>
> Key: MPIR-196
> URL: http://jira.codehaus.org/browse/MPIR-196
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Affects Versions: 2.2
> Reporter: William Ferguson
>
> One of the biggest problems (IMHO) when looking at project documentation is the inability to readily determine the age of a component or the age age of the documentation. Such information is often sued to make a decision on how relevant a new component might be.
> The Project Summary page generated by the Site plugin contains a Build Information section.
> This section identifies the GroupId, ArtifactId, Version, and Type.
> If it also published the DateTime at which a component was built then it solve the problem above.
--
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