We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In some use cases, that'd be useful to add some dependencies to the classpath for the exec goal. For example, one could write:
<plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <configuration> <executable>java</executable> <commandlineArgs>-classpath %classpath org.apache.camel.cdi.Main</commandlineArgs> <includePluginDependencies>true</includePluginDependencies> </configuration> <dependencies> <dependency> <groupId>io.astefanutti.camel.cdi</groupId> <artifactId>camel-cdi</artifactId> <version>${project.version}</version> </dependency> </dependencies> </plugin>
So that the additional dependency is contained in the %classpath variable.
%classpath
The text was updated successfully, but these errors were encountered:
A feature is necessary for adding additional dependencies but using pluginDependencies is a hack.
Sorry, something went wrong.
@slawekjaranowski I think this issue can be closed now that #432 is merged.
<includePluginDependencies>
Successfully merging a pull request may close this issue.
In some use cases, that'd be useful to add some dependencies to the classpath for the exec goal. For example, one could write:
So that the additional dependency is contained in the
%classpath
variable.The text was updated successfully, but these errors were encountered: