[
https://issues.apache.org/jira/browse/ONAMI-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated ONAMI-42:
--------------------------------
Attachment: ONAMI-42_proposal.patch
The proposed patch enables the DOAP generation in the parent pom while
generating the site; the power of that approach is that generates the releases
list as well, by retrieving them on the central repo!
I patched also the main site to demonstrate the usage.
WDYT?
> Publish DOAP descriptors for all components
> -------------------------------------------
>
> Key: ONAMI-42
> URL: https://issues.apache.org/jira/browse/ONAMI-42
> Project: Apache Onami
> Issue Type: New Feature
> Components: parent, site
> Affects Versions: parent-1
> Reporter: Simone Tripodi
> Assignee: Christian Grobmeier
> Fix For: parent-2
>
> Attachments: ONAMI-42_proposal.patch
>
>
> The ASF requires all projects publish the DOAP rdf file and I think that
> maintaining two set of metadata is an overkill - the main entry point is
> still the {{pom.xml}} - fortunately the
> [maven-doap-plugin|https://maven.apache.org/plugins/maven-doap-plugin] is
> friend of us in oder to have it automatically generated.
> My proposal is adopting the KISS approach that the Maven team already
> adopted: doap is generated and published on the
> [SITE|https://maven.apache.org/plugins/maven-doap-plugin/examples/with-site-plugin.html]
> rather than keep it stored on SVN.
> A patch proposal is coming.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
