Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2295

Creation of the third party libraries is not working anymore

    Details

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

      Description

      • when:
        • I want to generate the third party license pages on my local machine using the util/dependency-doc-creation/ module in the Optimize repo
      • then:
        • I get the following error:
          [ERROR] [ERROR] Some problems were encountered while processing the POMs:
          [ERROR] Unresolveable build extension: Plugin org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.sonatype.plugins:nexus-staging-maven-plugin:jar:1.6.8 @ 
          [ERROR] Non-resolvable import POM: Could not transfer artifact org.springframework:spring-framework-bom:pom:5.1.7.RELEASE from/to camunda-nexus (http://repository-ci-camunda-cloud.nexus:8081/content/groups/internal/): repository-ci-camunda-cloud.nexus @ org.camunda.optimize:parent:2.5.0-SNAPSHOT, /home/johannes/Camunda/camunda-optimize/pom.xml, line 59, column 19
          [ERROR] Non-resolvable import POM: Could not transfer artifact com.fasterxml.jackson:jackson-bom:pom:2.9.9 from/to camunda-nexus (http://repository-ci-camunda-cloud.nexus:8081/content/groups/internal/): repository-ci-camunda-cloud.nexus @ org.camunda.optimize:parent:2.5.0-SNAPSHOT, /home/johannes/Camunda/camunda-optimize/pom.xml, line 66, column 19
          [ERROR] 'dependencies.dependency.version' for org.springframework:spring-websocket:jar is missing. @ line 64, column 17
          [ERROR] 'dependencies.dependency.version' for org.springframework:spring-context-support:jar is missing. @ line 68, column 17
          ...
          
      • expected:
        • the third party license page generation works without erros

      Hint:
      The $

      {SETTINGS_PATH}

      variable is not correctly resolving the path to the settings.xml on every machine.

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            johannes.heinemann Johannes Heinemann
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: