infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Grigorov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-18741) Buildbot: maven-javadoc-plugin 3.1.x fails with Java 8 as default
Date Sat, 13 Jul 2019 20:20:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884467#comment-16884467
] 

Martin Grigorov commented on INFRA-18741:
-----------------------------------------

I've just committed r1047704 to https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/wicket.conf
adding JAVA_HOME for Wicket master branch builds for Java 11, 13 and 14.
Hopefully this will solve the issue.

> Buildbot: maven-javadoc-plugin 3.1.x fails with Java 8 as default
> -----------------------------------------------------------------
>
>                 Key: INFRA-18741
>                 URL: https://issues.apache.org/jira/browse/INFRA-18741
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Buildbot
>            Reporter: Andrea Del Bene
>            Priority: Major
>
> Hi,
> working on master branch (https://ci.apache.org/builders/wicket-master) of  Apache Wicket
we have upgraded maven-javadoc-plugin to the last version 3.1.0 and then to 3.1.1. Starting
with 3.1.0 we started to see this plugin failing generating JavaDocs for Wicket complaining
about not existing packages. For example:
> {quote}
> [ERROR] MavenReportException: Error while generating Javadoc: 
> Exit code: 1 - /home/buildslave/slave/wicket-master/build/wicket-util/src/main/java/org/apache/wicket/util/license/ApacheLicenseHeaderTestCase.java:32:
error: package org.slf4j does not exist
> import org.slf4j.Logger;
> {quote}
> Master branch requires Java 11 and is configured to use it via toolchain. After some
investigation I've been able to replicate this error running the build process with Java 8
(instead of Java 11) as default JDK. I suspect that we have the same configuration for the
master branch worker. With Java 11 as default JDK everything works fine.
> Is it possible to set JAVA_HOME to java 11 for master branch builder?
> Thank you. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message