You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/10/21 13:03:17 UTC

[GitHub] [maven] gnodet commented on pull request #840: [MNG-7038] Introducing project.topdir

gnodet commented on PR #840:
URL: https://github.com/apache/maven/pull/840#issuecomment-1286933973

   I fully agree to have a new `${project.topdir}` that won't go outside of the tree.
   For the `${project.topdir}/.mvn/settings.xml` use case, I'm not sure how that could be handled if multiple projects have different parameters.  If those projects are included in a bigger build, everything inside `.mvn/` becomes irrelevant I think, and all access to this directory should be done using `${maven.multiModuleDirectory}`.
   Note that we also have the `executionRootDir` which seems to reflect the upper parent path _being built_ (mainly when using `-f xxx` option).
   All those properties should be clearly defined and made public. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org