You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/21 01:47:00 UTC

[jira] [Resolved] (MASSEMBLY-689) Upgrade documentation according to best practice

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

Elliotte Rusty Harold resolved MASSEMBLY-689.
---------------------------------------------
    Resolution: Won't Fix

doesn't seem to be consensus on this

> Upgrade documentation according to best practice
> ------------------------------------------------
>
>                 Key: MASSEMBLY-689
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-689
>             Project: Maven Assembly Plugin
>          Issue Type: Improvement
>          Components: site
>    Affects Versions: 2.4
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>
> Currently the docs say things like this:
> {{It is common practice to create an assembly using the parent POM of a multimodule build. At times, you may want to ensure that this assembly also includes one or more of the module binaries.}} which is not best practice so it should be replaced by better explanations and the best practice. (http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)