Here's the skinny - I am using beta 5 as of 7-23-2002 - my maven.xml file overrides the compile goal to do nothing. (necessary)
my class files are in classes and source files in source. My build.properties has (among other things) maven.build.dest=classes maven.src.dir=source The project is very simple only one package with 8 files all in the same package and no dependencies. When I execute the javadoc goal I get 2 javadoc errors. Both start with No package, class, or source file found named .... One references the source path (which is correct) and one references the package (which is also correct). I ran maven verbose and I noticed that the javadoc command was being executed with an empty classpath. Any suggestions? (and yes the class files are there under the classes directory). The reason I am confused is that when I was using beta 4 it worked. I see in the plugin.jelly that the javadoc goal is getting a classpath refid (of maven.dependency.classpath )passed to it ( a la Ant) but I still am not quite sure how jelly works and how this reference gets set. I looked at the jelly tag library but did not see any mention on it. It looks like the jelly code for javadoc is calling the Ant javadoc task. What could be causing the classpath to not be set? thanks Doug -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
