[
https://issues.apache.org/jira/browse/MNG-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914080#comment-17914080
]
Guillaume Nodet commented on MNG-8523:
--------------------------------------
This is fixed when using the consumer POM though.
This is also not specific to CI friendly versions, but any property. When
using a property in a version, we do check that the property exists. However,
we don't check where it comes from. It may come from a model property or from
a user property. When a property is defined in the model, and this POM is used
as a dependency, the user properties from outside won't be used, because model
properties from the dependency take precedence over user properties (unlike
when building the POM). But this also means that when the original property is
defined using a user property, there's no model property to override it, which
means that the dependency version may be changed using a user property from CLI.
This looks really wrong.
This is definitely not new, and I'm not sure we can easily fix that in 3.x, but
we may be able to do so with 4.x in the consumer POM.
> CI Friendly versions are not inlined
> ------------------------------------
>
> Key: MNG-8523
> URL: https://issues.apache.org/jira/browse/MNG-8523
> Project: Maven
> Issue Type: Bug
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-rc-3
>
>
> The installed/deployed POMs using these are not inlined, and that means those
> are unusable. Same situation as with Maven 3, that forces use of flatten
> plugin to make them usable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
