Uploaded image for project: 'Talend Component Kit'
  1. Talend Component Kit
  2. TCOMP-1720

Changing the version breaks deployment to Studio

Apply templateInsert Lucidchart Diagram
    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 1.1.21
    • None
    • build

    • Talend Studio 7.1.1, 7.2.1,7.3.1 and TCK versions of 1.1.1+

    • Hide

      in the pom.xml edit the value in the <version> tag and then run mvn talend-component:deploy-in-studio -Dtalend.component.studioHome="${STUDIO_HOME}". You will get the error message from above.

      Show
      in the pom.xml edit the value in the <version> tag and then run mvn talend-component:deploy-in-studio -Dtalend.component.studioHome="${STUDIO_HOME}". You will get the error message from above.
    • All
    • Small

    Description

      In the pom.xml file if a developer changes the version of their component i.e. 0.0.1-SNAPSHOT to 0.0.2-SNAPSHOT and then tries to redeploy their component this causes the deploy to studio process to fail with the below. The additional parameter of -Dtalend.component.enforceDeploy=true does not work. The only solution is to manually edit the components-registration.properties file and remove the line for that component and then redeploy to Studio. This is going to cause major issues with our ISV and SI partners when they enhance or maintain their components.

      [ERROR] Failed to execute goal org.talend.sdk.component:talend-component-maven-plugin:1.1.19:deploy-in-studio (default-cli) on project yellowbrick-talend: Execution default-cli of goal org.talend.sdk.component:talend-component-maven-plugin:1.1.19:deploy-in-studio failed: Can't deploy this component. A different version '0.0.1-SNAPSHOT' is already installed.

      [ERROR] You can enforce the deployment by using -Dtalend.component.enforceDeploy=true

       

      Attachments

        Activity

          People

            emmanuel_g emmanuel gallois
            thbennett Thomas Bennett
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: