You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by GitBox <gi...@apache.org> on 2020/04/16 16:51:35 UTC

[GitHub] [jclouds] felfert edited a comment on issue #67: Fix javadoc generation on JDK >= 8

felfert edited a comment on issue #67: Fix javadoc generation on JDK >= 8
URL: https://github.com/apache/jclouds/pull/67#issuecomment-614765276
 
 
   Well, on a clean VM with JDK7 (java-1.7.0-openjdk-devel-1.7.0.251-2.6.21.0.el7_7.x86_64)
   everything builds fine here. Since I don't have access to your jenkins setup, I can only guess, that this setup might be broken in that respect. In fact, the build log shows, that jdk**1.8** is used to run maven but then this is apparently reverted by  using -Pjenkins which activates maven-toolchains-plugin which itself uses **~/.m2/toolchains.xml** to which I don't have access. So my hands are tied here.
   
   @gaul @nacx  Can one of you guys can provide me with that file so I can investigate further?
   @nacx : Maybe you introduced this jenkins profile for exactly that reason (Use jdk7 in order to solve the javadoc errors with JDK8 on jenkins)? If so, you could simply drop the -Pjenkins argument? 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services