commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (COMMONSSITE-81) commons-build-plugin README/CONTRIBUTING.md handle multi-modules
Date Fri, 02 Jan 2015 20:19:34 GMT

     [ https://issues.apache.org/jira/browse/COMMONSSITE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benedikt Ritter resolved COMMONSSITE-81.
----------------------------------------
    Resolution: Fixed

> commons-build-plugin README/CONTRIBUTING.md handle multi-modules
> ----------------------------------------------------------------
>
>                 Key: COMMONSSITE-81
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-81
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Build Plugin
>    Affects Versions: 1.5-SNAPSHOT
>            Reporter: Bernd Eckenfels
>            Assignee: Benedikt Ritter
>            Priority: Minor
>              Labels: patch
>         Attachments: multi-readme.patch
>
>
> The following patch will allow the commons-build-plugin to generate the correct README/CONTRIBUTING.md
even when we are in a multi-module scenario. 
> It will especially not use artifact-id for URLs (but `commons-${commons.componentId}`).
> This requires that the componentid does not contain "commons-" prefix (which is not given
for the plugin itself).
> There is a hack for creating a usefull maven artifact dependency. If the current project
contains "-project" it is removed as it is asumed that the main artifact you want to include
is not the meta-artifact. 
> (This "hack" works for VFS but it is a bit ugly, thats why I did not simply commit it).
> The patch also uses https for all the links.
> BTW: for VFS the generated 2 files in the top level directory work (besides the download-link
and apidoc).



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

Mime
View raw message