[jira] Updated: (MDOAP-11) How to handle release date?

["Vincent Siveton (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MDOAP-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Siveton updated MDOAP-11:
---------------------------------

    Attachment: MDOAP-11.patch

This patch is a workaround to handle created release date:
* read the repo artifactId page (ie http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-doap-plugin/ )
* apply a regular expression to find the last modified date on each directory i.e. version
* write the last modified date found in a <created/> tag

> How to handle release date?
> ---------------------------
>
>                 Key: MDOAP-11
>                 URL: http://jira.codehaus.org/browse/MDOAP-11
>             Project: Maven 2.x DOAP Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.0
>            Reporter: Vincent Siveton
>         Attachments: MDOAP-11.patch
>
>
> Actually, the mojo generates:
> {code:xml} 
> ...
>     <release>
>       <Version>
>         <name>PROJECT NAME - VERSION</name>
>         <revision>VERSION</revision>
>         <file-release>http://repo1.maven.org/maven2/org/apache/maven/...</file-release>
>       </Version>
>     </release>
> ...
> {code} 
> It should be nice to add the release created tag, ie
> {code:xml} 
> ...
>       <Version>
> ...
>         <created>2008-06-27</created>
>       </Version>
> ...
> {code} 
> Actually, the RepositoryMetadata doesn't have any notions of release date for a given version.

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