Jason, That worked very well. Thanks.
Doug >-----Original Message----- >From: Jason van Zyl [mailto:[EMAIL PROTECTED]] >Sent: Monday, July 29, 2002 1:02 PM >To: Turbine Maven Users List >Subject: Re: classpath for javadoc goal > > >On Mon, 2002-07-29 at 12:11, Doug Lochart wrote: >> > >> > >> > Looking at the plugin the classpath is set to >> > ${maven.dependency.classpath}. So the classpath of the >recently compiled >> >> I noticed this as well and when I tried setting >> ${maven.dependency.classpath} by hand in the build.properties or >> project.properties file, I get a message from maven that my override was >> ignored. >> > >No, you don't set ${maven.dependency.classpath} by hand. It always comes >from your stated dependencies in your project.xml. > >Try remove the entry in the the javadoc taskdef plugin.jelly file and >replace it with the following which adds the compiled project classes to >the classpath and let me know if that works. > > <javadoc > sourcepath="${pom.build.sourceDirectory}" > packagenames="${pom.package}.*" > destdir="${maven.javadoc.destdir}" > author="${maven.javadoc.author}" > private="${maven.javadoc.private}" > version="${maven.javadoc.version}" > use="${maven.javadoc.use}" > windowtitle="${title}" > doctitle="${title}" > bottom="${copyright}"> > <classpath> > <path refid="maven.dependency.classpath"/> > <path location="${maven.build.dest}"/> > </classpath> > </javadoc> > > > >-- >jvz. > >Jason van Zyl >[EMAIL PROTECTED] >http://tambora.zenplex.org > >In short, man creates for himself a new religion of a rational >and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For >additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
