Dan, I had the same issue for a custom plugin. What I did was to include my plugin's dependencies in the plugin's project.xml, then make sure the dependent jars were bundled along with the plugin when it was deployed.
Jeff On Thu, 02 Sep 2004, at 07:39:56 [GMT -0700] dan tran wrote: > Hello, > I have a custom plugin P which is called by a project A. > In plugin P, I have a tag which uses <ant:java> to invoke > a java class. > Calling plugin P's tag from project A results in a ClassNotFoundException, > unless I include plugin P's denpendencies in project A > In previous post, I have the similar problem when dealing with > plugin's properties not seeing by plugin's tag > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=15788 > Is there similar solution for this situtation. I just hate to include > my custom plugin's dependencies that every project that needs to > call the tag. > Big thanks > -Dan -- mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
