Ruchir Sanghavi commented on MNG-5586:

This would be highly beneficial. I see it as a bug in maven - the pom.xml 
should reflect how the deployed artefact was created and which versions were 
used (as they could be overriden via command line argument property variables 
or using profiles). The problem comes when something is referencing that 
artefact, and tries to pull its dependencies, it will pull the wrong 
dependencies because pom.xml will not know which profile to use or which 
property was overriden when doing mvn install deploy. Hope this makes sense? 

> Deploy effective pom
> --------------------
>                 Key: MNG-5586
>                 URL: https://issues.apache.org/jira/browse/MNG-5586
>             Project: Maven
>          Issue Type: Improvement
>          Components: Deployment
>            Reporter: nicolas de loof
> When deploying pom for an artifact, maven deploys the actual file used to 
> build. As this one can define profiles, and build can rely on command line 
> properties that change actual project model, the deployed pom.xml may not 
> reflect the one used by maven to build the project. Also, this prevent 
> changes to happen in pom.xml format (wildcard exclusion for sample) without 
> breaking compatibility.
> Maven should deploy effective pom when artifact doesn't define pom packaging 

This message was sent by Atlassian JIRA

Reply via email to