Multi-module project doesn't work when parent isn't in repo

[Randgalt]

NOTE: I've only tried this with groovy

I have a standard multi module project ala:

src
pom.groovy
module1
             src
             pom.groovy
module2
            src
            pom.groovy

Performing "mvn compile" from the root produces: "[FATAL] Non-resolvable parent POM for..."

However, if I then do: "mvn -N install" from the root and then do "mvn compile" it works fine.

[Randgalt]

FYI - adding:

relativePath '../pom.groovy'

To the parent section fixes the problem

[jvanzyl]

Yah, that's still a bug. It's not being defaulted correctly.

[Randgalt]

Any timeframe for a fix or is there a workaround? It's a hard stop for me right now.

Edit: I should say that I'm using the translator to build the groovy files which is why I can't just add the relativePath

[jvanzyl]

I can definitely look at it on Monday. Can you work around in the project you're working on adding the relativePath manually, or change the translator to output it?

[Randgalt]

I'll look at having the translator do it.

[Randgalt]

Hmm - this is hard to do. The mvn runtime seems to be using an embedded reference to TeslaModelTranslator. My changes aren't getting used.

[jvanzyl]

I can take a look at anything you have tonight.

[szantopeter]

@jvanzyl @Randgalt Have you had any chance to look into this? I am still facing the issue with a multi module groovy project. You can find the project here (also the build logs in travis)

https://github.com/ExampleDriven/maven-polyglot-groovy-example

Adding relativePath did not help.

Note : This happens with groovy and scala build scripts as well

[szantopeter]

This is a showstopper bug, as a new multi module project can't be compiled @jvanzyl @Randgalt Have you had any luck with this?