[
https://issues.apache.org/jira/browse/MNG-8211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875789#comment-17875789
]
Tamas Cservenak commented on MNG-8211:
--------------------------------------
The limitation of "setting property" is clearly explained for example here:
https://www.mojohaus.org/properties-maven-plugin/#plugin-limitations newly
added properties by plugin are only available for other (downstream) plugins
like m-resource-p for _filtering resources_.
Also, Nisse tries to explain this as well: https://github.com/maveniverse/nisse
* nisse plugin "just makes properties available for other plugins"
* nisse extension "makes properties available as user properties (as user would
type them -Dxxx=xx) and also inlines POM file as well, hence plain
install/deploy works as well". But this is doable ONLY from an extension.
> Maven should fail builds that use CI Friendly versions but have no values set
> -----------------------------------------------------------------------------
>
> Key: MNG-8211
> URL: https://issues.apache.org/jira/browse/MNG-8211
> Project: Maven
> Issue Type: Bug
> Components: Core
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 4.0.0-beta-4, 3.9.10
>
>
> As otherwise it is just source of confusion, Maven will "happily" install and
> deploy artifacts as {{G:A:$revision}} and this is 100% NOT what users wants.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
