Skip to content
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

Building with Java 1.8 throws javadoc creation error #30

Closed
vikubel opened this issue Jan 13, 2016 · 1 comment
Closed

Building with Java 1.8 throws javadoc creation error #30

vikubel opened this issue Jan 13, 2016 · 1 comment
Labels

Comments

@vikubel
Copy link

vikubel commented Jan 13, 2016

With Java 1.8, building using command :

mvn clean package assembly:single

throws following exceptions and fails:

[ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:205)
[ERROR] at com.sun.tools.javadoc.Main.execute(Main.java:64)
[ERROR] at com.sun.tools.javadoc.Main.main(Main.java:54)
[ERROR] javadoc: error - java.lang.IllegalArgumentException
[ERROR]
[ERROR] Command line was: <somepath>\Java\jdk1.8.0_60\jre\..\bin\javadoc.exe -J-Dhttp.proxySet=true -J-Dhttp.proxyHost=foo.com -J-Dht
tp.proxyPort=nn "-J-Dhttp.nonProxyHosts=\"localhost|*.foo.com\"" @options @packages
[ERROR]
[ERROR] Refer to the generated Javadoc files in '<somepath>\jrobotremoteserver\target\apidocs' dir.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Solution:
Reference:

Need to build using following command:

mvn  clean package assembly:single -Dmaven.javadoc.skip=true
@ombre42 ombre42 added the bug label Jan 13, 2016
@ombre42
Copy link
Collaborator

ombre42 commented Jan 13, 2016

Thanks for reporting this. Eclipse added some of these Javadoc items. And sometimes I didn't feel like elaborating on them. Unfortunate that javadoc issues cause a build to fail instead of generating warnings. At least it is easy to fix :)

Hi-Fi added a commit that referenced this issue Jan 14, 2020
Fixes #46

Fixes #34

Fixes #30
@Hi-Fi Hi-Fi closed this as completed in c998b0d Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants