-
Notifications
You must be signed in to change notification settings - Fork 189
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
tycho-document-bundle-plugin tests depend on PATH #471
Labels
Milestone
Comments
Maybe we can check how the maven-javadoc-plugin works? |
Bananeweizen
added a commit
to Bananeweizen/tycho
that referenced
this issue
Jan 2, 2022
Use also JAVA_HOME to find a suitable javadoc executable. That logic is similar to what plexus JavacCompiler does.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After lots of trial and error I've just found one reason for failing integration tests. The document-bundle-plugin tests run javadoc by just invoking the javadoc executable without using any path. Therefore whatever is first on the local PATH environment variable will be called. Since there are subtle differences between Java 8 (what I had on the path) and Java 11 Javadoc, the verification groovy script fails with some files not found, some files not matching content and finally even NoClassDefFoundError (for the Doclet).
What is a good way to avoid that? I can imagine these solutions:
Any better ideas?
The text was updated successfully, but these errors were encountered: