Plug-ins are not part of your code and stuff in the dependency section
has no affect on plug-ins.
If foo is "provided", you probably have to put it in the Java library
folder or the Maven folder.
You need to go back to the plug-in documentation and see how to include
libraries in plug-ins.
I don't write plug-ins so this is about as far as I can help.
Ron
On 18/01/2014 2:35 PM, tanuj...@gmail.com wrote:
Hello Rusty WRight
I have created a mvn plugin called "foo" that needs a jar file say "xyz.jar"
in order to compile and run. in the pom file of plugin project foo I have
provided xyz.jar with "provided" scope in the dependencies section. I do not
want to package the xyz.jar file in the plugin. The plugin "foo" will be
triggered by another project say "bar" in its install phase. so I added the
plugin foo in the <build><plugins><plugin>...</plugin></plugins></build>
section of the project bar. project bar has the dependency of "xyz.jar" in
its <dependencies> section. when I run install goal the classes present in
the xyz.jar and which are refered by the plugin foo throw
ClassNotFoundException at Runtime.
Please let me know how to resolve this.
--
View this message in context:
http://maven.40175.n5.nabble.com/dependencies-needed-by-plugin-tp5781651.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
