You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2021/09/12 15:11:00 UTC

[jira] [Commented] (MNG-7170) Allow to associate pomFile/${basedir} with DefaultProjectBuilder.build(ModelSource, ...)

    [ https://issues.apache.org/jira/browse/MNG-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413729#comment-17413729 ] 

Hudson commented on MNG-7170:
-----------------------------

Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.8.x #67

See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.8.x/67/

> 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
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.8.2
>
>
> 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)