Hi Ashish,
the dependencies of the project-pom are not part of the maven classpath.
That means that your plugin does not run in a JVM where that jars have
been loaded. Your plugin will run having its own dependencies loaded
(those of plugin-pom), not those of the project that is currently under
bui
Hi,
I have a custom maven plugin that does not seem to be picking up a
compile time dependency. The project structure
is something like
super-pom:
defines the plugin build usage - goal/phase(generate-sources)
project-pom:
inherits from super-pom.
defines a default(compile scope)