docker:build to use a temporary directory inside the ${basedir}/target to avoid multi-project build issues

[jstrachan]

I've just hit an issue where a second docker image in a build got jars from a previous docker build :)

It seems like the temporary folder docker:build is using doesn't take into account the current ${basedir} from the project module.

It'd be good to make the default use ${basedir}/target/docker/... or something?

[jstrachan]

I think we need to add ${basedir}/ to these properties
https://github.com/rhuss/docker-maven-plugin/blob/master/src/main/java/org/jolokia/docker/maven/BuildMojo.java#L50-50
https://github.com/rhuss/docker-maven-plugin/blob/master/src/main/java/org/jolokia/docker/maven/BuildMojo.java#L45

[jgangemi]

i thought $basedir was always assumed if the path is relative

[jstrachan]

It doesn't seem to be in a multi-maven build; I can see the docker plugin using the exact output folder for every module ;)

[jgangemi]

yeah - i just noticed that myself but adding in $basedir where you suggested doesn't work but i have another idea.

[jgangemi]

ok - i have a fix for this. let me put together a pull request.

[jstrachan]

great thanks!

FWIW as a workaround I added this to my pom.xml:

        <docker.target.dir>${basedir}/target/docker-plugin</docker.target.dir>

https://github.com/fabric8io/quickstarts/blob/master/pom.xml#L79

which seems to be a work around

[jgangemi]

fixed - if you want to build a local copy, feel free to pull from my branch until @rhuss merges the changes in.

[jstrachan]

thanks @jgangemi

[rhuss]

fixed in 0.11.2