Unable to build when maven project is in a sub-directory

[ctron]

It seems that the java build has an issue when the source code of the maven project is inside a sub-directory of the repository.

There is a check in the assemble script which checks for the existence of the pom.xml, but this uses S2I_SOURCE_DIR, which it seems cannot be overridden by the build.

My proposal would be to add some additional kind of environment variable (e.g. SOURCE_ROOT_DIR) which defaults to . and can be overridden.

[rhuss]

Sounds fair to me. Fancy doing a PR ?

The question is, whether we should also allow for a path to a pom.xml (by setting a POM env var and adding a -f $POM to the maven command line in case), which would keep the working directory still at S2I_SOURCE_DIR.

For the directory env var name I'd suggest something like POM_DIR (for cd'ing into the dir and running a plain maven) and POM_FILE for pointing to a pom.xml (and keeping the cd at S2I_SOURCE_DIR)

[ctron]

I will look into this.

[cmoulliard]

Do we plan to support this option which is needed when by example we have a maven project having several maven modules without parent pom.xml ?

[ctron]

I think this should be possible by using -f subdirectory in the MAVEN_ARGS variable. And then maybe tweaking the ARTIFACT_DIR in addition.