[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709762#comment-17709762
]
ASF GitHub Bot commented on MNG-7038:
-------------------------------------
gnodet commented on PR #1061:
URL: https://github.com/apache/maven/pull/1061#issuecomment-1500561296
> > Some of the use cases involve arguments interpolation, so this has to be
done very early in the process.
>
> That are probably just other use-cases that where requested! I just wanted
remind of the original request, that only wanted to make `multiModuleDirectory`
official to be **used inside a pom**, it was never asked to work on commandline
arguments, and at the point where the **model(!)** is read the location is well
known and there are no inconsistency and it is early enough for this use-case.
JIRA seems down for me, but I can point to MNG-5659 or
https://github.com/apache/maven-mvnd/issues/813#issuecomment-1466916434
> > Also, I disagree that this is weird somehow. I think it's actually
mapping quite well with the property isRootProject()
>
> I think you mean
`org.apache.maven.project.MavenProject.isExecutionRoot()`? Beside from Maven
developers I assume no one ever has heard of it and I can't find the term in
the current maven documentation anywhere. Beside that, its currently defined as
the project that is the one where I executed maven.
I was referring to
https://github.com/apache/maven/pull/1061/files#diff-5e32d3e141f6d87a19ff7f26d7ff4f2d427a8d98622e71ef24a1168772d23e13R117
> Introduce public property to point to a root directory of (multi-module)
> project
> --------------------------------------------------------------------------------
>
> Key: MNG-7038
> URL: https://issues.apache.org/jira/browse/MNG-7038
> Project: Maven
> Issue Type: Improvement
> Reporter: Envious Guest
> Priority: Major
> Fix For: Issues to be reviewed for 4.x
>
>
> This is a request to expose a property *maven.multiModuleProjectDirectory*
> which is currently internal (or introduce a brand new one with analogous
> functionality).
> * For a single-module project, its value should be same as *project.basedir*
> * For multi-module project, its value should point to a project.basedir of a
> root module
> Example:
> multi-module // located at /home/me/sources
> +- module-a
> +- module B
> Sample multi-module/pom.xml:
> {{<project>}}
> {{ <parent>}}
> {{ <groupId>com.acme</groupId>}}
> {{ <artifactId>corp-parent</artifactId>}}
> {{ <version>1.0.0-RELEASE</version>}}
> {{ </parent>}}
> {{ <groupId>com.acme</groupId>}}
> {{ <artifactId>multi-module</artifactId>}}
> {{ <version>0.5.2-SNAPSHOT</version>}}
> {{ <modules>}}
> {{ <module>module-a</module>}}
> {{ <module>module-b</module>}}
> {{ </modules>}}
> {{</project>}}
> The property requested should return /home/me/sources/multi-module,
> regardless of whether it's referenced in any of the child modules (module-a,
> module-b) or in multi-module.
> Note that multi-module itself has parent (e.g. installed in a local
> repository), so the new property should be smart enough to detect it and
> still point to /home/me/sources/multi-module instead of the local repository
> where the corp-parent is installed.
> The use-case for such a property could be to have a directory for combined
> report of static analysis tools. Typical example - jacoco combined coverage
> reports.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
