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

Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/12/28 00:54:49 UTC

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

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

Michael Osipov commented on MASSEMBLY-689:
------------------------------------------

Why is that a bad practice?

> 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
(v6.3.4#6332)