[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    [jira] [Created] (COMMONSSITE-81) commons-build-plugin README/CONTRIBUTING.md handle multi-modules
From:       "Bernd Eckenfels (JIRA)" <jira () apache ! org>
Date:       2014-12-31 17:52:13
Message-ID: JIRA.12764407.1420048314000.122613.1420048333122 () Atlassian ! JIRA
[Download RAW message or body]

Bernd Eckenfels created COMMONSSITE-81:
------------------------------------------

             Summary: 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
            Priority: Minor


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)


[prev in list] [next in list] [prev in thread] [next in thread]