We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Steps to reproduce: change outputFormat to javadoc in maven plugin 0.9.7.
Then
mvn pre-site
<plugin> <groupId>org.jetbrains.dokka</groupId> <artifactId>dokka-maven-plugin</artifactId> <version>0.9.7</version> <executions> <execution> <phase>pre-site</phase> <goals> <goal>dokka</goal> </goals> <configuration> <outputFormat>javadoc</outputFormat> </configuration> </execution> </executions> </plugin>
Manual addition of $JAVA_HOME/lib/tools.jar to classpath fixes it, so I'm assuming the dependency was not in fatjar for some reason.
The text was updated successfully, but these errors were encountered:
I used to think tools.jar is in the classpath for jdk.. Perhaps we can add system dependency as well to avoid issue
Sorry, something went wrong.
Perhaps we can do http://stackoverflow.com/a/3080695
Yeah, should do the trick
Fixed in 62cd241
tools.jar (#125), Fixes #85, #58
25b9aa9
Added hack to adjust publishing pom for maven Added hack to load tools.jar for cli
No branches or pull requests
Steps to reproduce: change outputFormat to javadoc in maven plugin 0.9.7.
Then
Manual addition of $JAVA_HOME/lib/tools.jar to classpath fixes it, so I'm assuming the dependency was not in fatjar for some reason.
The text was updated successfully, but these errors were encountered: