[
https://issues.apache.org/jira/browse/MNG-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359826#comment-17359826
]
Mickael Istria commented on MNG-7170:
-------------------------------------
I wrote a test that reproduces the issues for 3.8.1:
[https://github.com/mickaelistria/maven/tree/test-MNG-7170-3.8.1
]Same test against master seems to pass:
[https://github.com/mickaelistria/maven/tree/test-MNG-7170-4.0|https://github.com/mickaelistria/maven/tree/test-MNG-7170-3.8.1]
I'll keep investigating sort out which commit does introduce the probable fix
to find out whether this cna be leveraged downstream easily, or whether a 3.8.2
seems to be a requirement.
> Allow to associate pomFile/${basedir} with
> DefaultProjectBuilder.build(ModelSource, ...)
> ----------------------------------------------------------------------------------------
>
> Key: MNG-7170
> URL: https://issues.apache.org/jira/browse/MNG-7170
> Project: Maven
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.8.1
> Reporter: Mickael Istria
> Priority: Major
>
> In LemMinX-Maven Language Server for pom.xml files, we're building models
> from "working copy" (unsaved) pom files. We do so by invoking
> {code}DefaultProjectBuilder.build( ModelSource modelSource,
> ProjectBuildingRequest request ){code}
> One pitfall is that this cascades to pomFile being null for the Model, and as
> a result {code}${basedir}{code} is not resolved.
> One could expect that the {code}ModelSource2.getLocationURI(){code} could be
> used to derive the pomFile when possible. LemMinX-Maven happens to properly
> set this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
