Yes.
> -----Original Message----- > From: Nathan Coast [mailto:[EMAIL PROTECTED] > Sent: Monday, 15 September 2003 2:47 PM > To: Maven Users List > Subject: Re: plugin dependencies > > > cheers Brett, > > this only works if the project has the dependency included in the > project.xml rather than defining the dependency in the plugin's > project.xml. Is this right? > > Brett Porter wrote: > > > Remove the <classloader> properties, and add this to the java call: > > classpathref="maven.dependency.classpath" > > > > Cheers, > > Brett > > > > > >>-----Original Message----- > >>From: Nathan Coast [mailto:[EMAIL PROTECTED] > >>Sent: Monday, 15 September 2003 2:08 PM > >>To: Maven Users > >>Subject: plugin dependencies > >> > >> > >>Hi > >> > >>I have a plugin that uses 3rd party classes. How do I make these > >>classes available to the plugin? I'm getting a > NoClassDefFoundError > >>when calling targets within the plugin. > >> > >>I'm calling the 3rd party classes like this: > >><ant:java classname="weblogic.Deployer" fork="true"> > >> <arg>blah blah........ > >> > >>I have this element in the plugin's project.xml > >> > >> <dependency> > >> <id>weblogic</id> > >> <version>8.1</version> > >> <properties> > >> <classloader>root</classloader> > >> </properties> > >> </dependency> > >> > >>cheers > >>Nathan > >> > >> > >> > >> > >>------------------------------------------------------------ > --------- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
