Note that the issue could still appear if you are defining a sub module of the first module.
parent->plugins->myplugin might not be able to find it.
A workaround could be to keep ${project.build.directory} in parent project.
But define in plugins pom.xml${project.parent.build.directory} and in myplugin pom.xml${project.parent.parent.build.directory}.
@rmuir I think that this PR should be pulled in before we refactor the main repository. IIRC if you want to run some tests, you will need to mvn install this branch first locally.
When using
dev-tools
in a sub project, maven can not find thedev-tools
dir inside the sub module it self.To fix that, we need to set that
elasticsearch.tools.directory
is actually using the parent dir.Note that the issue could still appear if you are defining a sub module of the first module.
parent->plugins->myplugin
might not be able to find it.A workaround could be to keep
${project.build.directory}
in parent project. But define in pluginspom.xml
${project.parent.build.directory}
and in mypluginpom.xml
${project.parent.parent.build.directory}
.@rmuir WDYT?