[
https://issues.apache.org/jira/browse/MNG-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485872#comment-17485872
]
Maarten Mulders commented on MNG-7244:
--------------------------------------
Rather than failing the build, would it be OK to just continue silently? Just
like we would do when the user has an expression {{foo.bar.baz}} that can't be
resolved: we continue the build, and the expression ends up in the eventual
Project Object Model.
It would make the code a lot simpler if we could do that. Right now, there's
code especially crafted to see if {{pom.X}} would resolve against {{project}},
and then logging the warning. Getting rid of that would make the code base more
simple, especially when we combine it with MNG-7404.
> Change from deprecated WARNING to FAIL the build for usage of pom.X
> placeholders
> --------------------------------------------------------------------------------
>
> Key: MNG-7244
> URL: https://issues.apache.org/jira/browse/MNG-7244
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 4.0.0-alpha-1
> Reporter: Karl Heinz Marbaise
> Assignee: Maarten Mulders
> Priority: Minor
> Labels: must-be-in-4.0.0-alpha-1
> Fix For: 4.0.x-candidate
>
>
> Currently we produce a {{WARNING}} in case of using {{pom.version}} or alike.
> I would suggest to change {{WARNING}} into a failing build in such use cases.
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for 'com.soebes.examples.j2ee:appasm:pom:1.0-SNAPSHOT'
> [WARNING] The expression ${pom.version} is deprecated. Please use
> ${project.version} instead.
> {code}
> WDYT?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
