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

Steve Wong updated MNG-7023:
----------------------------
    Description: 
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, so should this functionality be avoided?

 

  was:
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: 

 

 

 


> pluginManagement in profiles undocumented for maven 3.x
> -------------------------------------------------------
>
>                 Key: MNG-7023
>                 URL: https://issues.apache.org/jira/browse/MNG-7023
>             Project: Maven
>          Issue Type: Bug
>          Components: Profiles
>    Affects Versions: 3.x / Backlog
>            Reporter: Steve Wong
>            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, so should this functionality be 
> avoided?
>  



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

Reply via email to