There are other ways to do this 99% of the time. Can you bundle up the whole plugin source and post it to JIRA? I'd like to fix this before RC3.
- Brett > -----Original Message----- > From: Nathan Coast [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 4 May 2004 11:19 AM > To: [EMAIL PROTECTED] > Subject: plugins / root classloader > > > Hi, > > I have a plugin that used to work with rc1 but now > fails with a no class def error with rc2. > > The plugin has classes that extend junit classes. The > plugin has a dependency like this: > > <dependency> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > <version>3.8.1</version> > <properties> > <classloader>root</classloader> > </properties> > <type>jar</type> > </dependency> > > without the classloader root element, the plugin fails > with NoClassDef.... on the junit classes. The plugin > has classes which are needed by junit at runtime. The > classes are in > plugins/maven-junitejb-plugin-1.0/com/foo/bar but > maven is unable to locate them. What do I have to do > in order to make the classes within the plugin > available at plugin execution? > > thanks > Nathan > > > > > __________________________________ > Do you Yahoo!? > Win a $20,000 Career Makeover at Yahoo! HotJobs > http://hotjobs.sweepstakes.yahoo.com/careermakeover > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
