Thanks. Turns out that in my project POM file, if I add a <dependencies><dependency> section right below the <version> tag for the plugin and place the tools.jar dependency there, I don't need to modify the POM for the plugin.
I had tried this before but placed the added dependencies section AFTER the <executions> section and this didn't work for me. Adding the dependency BEFORE the <executions> section however does work. Jim dan tran wrote: > > use maven profile > > http://maven.apache.org/guides/introduction/introduction-to-profiles.html > -D > > -- View this message in context: http://www.nabble.com/JAX-WS-plugin-apt-NoClassDefFound-error-tf3396095s177.html#a9459700 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
