When starting Optimize I get a warning

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 2.5.0
    • Affects Version/s: None
    • Component/s: backend
    • None

      The following error message shows up when starting Optimize 2.5.0-alpha2:

      17:18:25.309 [main] WARN  org.glassfish.jersey.internal.Errors - The following warnings have been detected: WARNING: Return type, org.camunda.optimize.dto.optimize.rest.report.EvaluationResultDto<?, ?>, of method, public org.camunda.optimize.dto.optimize.rest.report.EvaluationResultDto<?, ?> org.camunda.optimize.rest.SharingRestService.evaluateReport(java.lang.String), is not resolvable to a concrete type.
WARNING: Return type, org.camunda.optimize.dto.optimize.rest.report.EvaluationResultDto<?, ?>, of method, public org.camunda.optimize.dto.optimize.rest.report.EvaluationResultDto<?, ?> org.camunda.optimize.rest.SharingRestService.evaluateReport(java.lang.String,java.lang.String), is not resolvable to a concrete type.
WARNING: Return type, org.camunda.optimize.dto.optimize.rest.report.EvaluationResultDto<?, ?>, of method, public org.camunda.optimize.dto.optimize.rest.report.EvaluationResultDto<?, ?> org.camunda.optimize.rest.ReportRestService.evaluateReportById(javax.ws.rs.container.ContainerRequestContext,java.lang.String), is not resolvable to a concrete type.
WARNING: Return type, org.camunda.optimize.dto.optimize.rest.report.EvaluationResultDto<?, ?>, of method, public org.camunda.optimize.dto.optimize.rest.report.EvaluationResultDto<?, ?> org.camunda.optimize.rest.ReportRestService.evaluateProvidedReport(javax.ws.rs.container.ContainerRequestContext,org.camunda.optimize.dto.optimize.query.report.ReportDefinitionDto), is not resolvable to a concrete type.

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: