Open PiotrMachner opened 8 years ago
Hi Piotr,
includePluginDependencies
in the plugin configuration?executableDependency
in the plugin configuration?@ikysil I have the same problem as @PiotrMachner. Neither I use includePluginDependencies
nor executeableDependency
.
For me it helped to introduce our company repository also in pluginRepositories section. Despite the dependency for a plugin looks like a regular dependency it is being searched in plugin repository which is by default central maven repository. See Getting Maven missing dependency errors when compiling ...
In my company we're using an artifactory which everybody has configured as a repository in their own ~.m2\repository\settings.xml file (and this works).
But for some reason the exec-maven-plugin ignores / dislikes this repository. In my exec plugin configuration I've got a dependency that is in the mentioned repository:
and when I run the build, maven correctly resolves the dependency from the company repository but the exec plugin fails after trying to get the dependency from the global maven repositories (but not from the company repository):
When inside my local repository I delete the _remote.repositories files for my dependency as suggested here the build passes. So it appears as if the exec plugin for some reason 'disliked' the company repository.
Any help would be appreciated. Thanks, Piotr