[jira] [Closed] (MNGSITE-431) pluginManagement in profiles undocumented for maven 3.x

["Sylwester Lachiewicz (Jira)" <ji...@apache.org>]

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

Sylwester Lachiewicz closed MNGSITE-431.
----------------------------------------
    Resolution: Fixed

> pluginManagement in profiles undocumented for maven 3.x
> -------------------------------------------------------
>
>                 Key: MNGSITE-431
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-431
>             Project: Maven Project Web Site
>          Issue Type: Improvement
>            Reporter: Steve Wong
>            Assignee: Elliotte Rusty Harold
>            Priority: Minor
>
> I was surprised to find that specifying a pluginManagement element in a profile works, because this is not listed in the maven 3.x documentation page: [https://maven.apache.org/guides/introduction/introduction-to-profiles.html]
> {quote} * a subset of the {{<build>}} element, which consists of:
>  ** {{<defaultGoal>}}
>  ** {{<resources>}}
>  ** {{<testResources>}}
>  ** {{<finalName>}}{quote}
> With a bit of googling, I came across the docs for maven2, which does allow it: [https://cwiki.apache.org/confluence/display/MAVENOLD/Build+Profiles]
> {quote}{{build}} _({{pom.xml}})_
>  * {{plugins}}
>  * {{pluginManagement}}{quote}
>  and the 3.6.3 model reference allows it: [https://maven.apache.org/ref/3.6.3/maven-model/maven.html]
> {quote}line 378: <profiles>
> line 379:  <profile>
> line 399:  <build>
> line 422:   <pluginManagement>
> {quote}
>  Is the undocumented behaviour correct, or should this functionality be avoided?
>  



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