You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/10/19 13:27:00 UTC
[jira] [Commented] (AMBARI-24806) Swagger spec for Ambari REST API
generation is failing
[ https://issues.apache.org/jira/browse/AMBARI-24806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656804#comment-16656804 ]
Hudson commented on AMBARI-24806:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10234 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10234/])
AMBARI-24806. Upgrading swagger maven plugin version (#2491) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=1ac3444e9755113df2cb9db6b5fa24bdd88925cc])
* (edit) ambari-project/pom.xml
> Swagger spec for Ambari REST API generation is failing
> ------------------------------------------------------
>
> Key: AMBARI-24806
> URL: https://issues.apache.org/jira/browse/AMBARI-24806
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.8.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Running the following command failed with the following error:
>
> {noformat}
> mvn -Del.log=WARN -Dcheckstyle.skip -Dfindbugs.skip -Drat.skip -DskipTests -DfailIfNoTests=false -am -pl ambari-server clean install
> ...
> [ERROR] Failed to execute goal com.github.kongchen:swagger-maven-plugin:3.1.4:generate (default) on project ambari-server: Conflicting setter definitions for property "requestBody": org.apache.ambari.server.orm.entities.RequestScheduleBatchRequestEntity#setRequestBody(1 params) vs org.apache.ambari.server.orm.entities.RequestScheduleBatchRequestEntity#setRequestBody(1 params) -> [Help 1]
> {noformat}
>
> According to this thread t[his is a known issue|https://github.com/FasterXML/jackson-databind/issues/1251] in swagger
> Upgrading the swagger plugin to 3.1.5 solves the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)