-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Taglet blocks javadoc generation with ClassNotFoundException #19
Comments
The I just tested an Ant build in IntelliJ targeting Java 1.8 and it worked as expected (with no changes). Note that you need to keep the @jeremydouglass Can you give me more details on your environment so I can try to see why it failed for you? |
I'm developing a Processing Library for the first time and I got this problem too while generating the javadoc. Everything works correctly but the docs aren't created automatically.
|
I was using Eclipse 4(.8?) on OS X 10.12. I believe the issue may have been (?) that I had JDK 10 and was using it to target 8. This largely works, except when it doesn't. Possibly related: processing/processing-library-template#20 |
same error. The
|
I also have this problem. If you look at: Then it states:
The file I suspect that the file For now I commented the following lines in
|
This is work in progress, but if I change generate.javadoc to the following: <target name="generate.javadoc" if="is.normal">
<!-- create the java reference of the Library -->
<javadoc sourcepath="${project.src}"
destdir="${project.tmp}/${project.name}/reference"
classpath="${classpath.local.location}/core.jar;{project.bin}"
/>
</target> And in terminal: But it creates a javadoc! |
When I run the Processing template targeting Java SE-1.8, the
In the Processing Library template there is a file
It begins with
I think that in Java 8+ that would instead would be:
...I'm not sure if there are other changes that would need to be made.
I am not familiar with doclets and Taglets -- looking over the code, it isn't clear to me why ExampleTaglet would actually be used -- although is referenced in Ant's build.xml:
Anyway, when it fails the documentation as a whole fails to build.
Assuming this is a problem for others, it seems like either ExampleTaglet should be fixed or it should be removed from build.xml to not block javadoc generation.
My solution was to remove the above line from build.xml.
The text was updated successfully, but these errors were encountered: