[ 
https://issues.apache.org/jira/browse/PDFBOX-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535198#comment-14535198
 ] 

Sebb commented on PDFBOX-2790:
------------------------------

The DOAP files don't make much sense in code releases, so I don't think there's 
any point in fixing them in branches.

Rather than store the DOAP in a code location, why not store it somewhere else, 
e.g. in the source area for building the site?
The projects file 
https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml
 can be changed to pick up the DOAP from somewhere like

http://pdfbox.apache.org/doap_PDFbox.rdf

This has the advantage that any changes to repo URLs won't affect the build of 
the projects.apache.org site.
But of course updates won't be seen unless the site is republished.

> Syntax error in DOAP file release section
> -----------------------------------------
>
>                 Key: PDFBOX-2790
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-2790
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 2.0.0
>         Environment: 
> http://svn.apache.org/repos/asf/pdfbox/trunk/doap_PDFBox.rdf
>            Reporter: Sebb
>            Assignee: Tilman Hausherr
>              Labels: DOAP
>             Fix For: 2.0.0
>
>
> DOAP files can contain details of multiple release Versions, however each 
> must be listed in a separate release section, for example:
> {code}
> <release>
>       <Version>
>         <name>Apache XYZ</name>
>         <created>2015-02-16</created>
>         <revision>1.6.2</revision>
>       </Version>
> </release>
> <release>
>       <Version>
>         <name>Apache XYZ</name>
>         <created>2014-09-24</created>
>         <revision>1.6.1</revision>
>       </Version>
> </release>
> {code}
> Please can the project DOAP be corrected accordingly?
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to