Hopefully our conversation will benefit others who've experienced the same
issue, so thank you for showing that it works in some cases. I think the
reason someone might want their projects all in the same directory is
because Eclipse has issues with nested project structures.
@Lasse, the
> It seems the goal assumes that child modules sit in nested
> directories.
Well, that might be the case. I have never tested any other scenario
because this is how I organise my Maven projects. Neither am I a Maven
expert nor did I claim that my solution works for everybody in every
case. I just
Am 2021-02-05 um 18:52 schrieb Andres Almiray:
@Tamás: Right, should had explained the use case. I want to deploy all
artifacts to a local directory so that I can inspect everything which will
be deployed given certain conditions.
I managed to do that by forcing a stable, absolute directory as
It seems the goal assumes that child modules sit in nested directories.
Unzip and run mvn validate in the root directory, and you'll see the root
location for project sarek is incorrect.
Delany
On Sat, 6 Feb 2021 at 14:28, Alexander Kriegisch
wrote:
> Maybe I misunderstand you, but for me this
Maybe I misunderstand you, but for me this works nicely in a module which has a
parent of type POM which has the root (also of type POM) as parent. I.e. the
root POM is the grandparent. I have no issues, as long as the property is
declared in the root as shown in the project I linked to.
--
This only works if the parent is the root. If you extend to a third level
of pom, it will report the rootlocation as the project directory.
Delany
On Sat, 6 Feb 2021 at 04:22, Alexander Kriegisch
wrote:
> I had some discussion with Karl Heinz Marbaise about
> maven.multiModuleProjectDirectory a
