Details

      Description

      First Run Should:

      1. update Talend Eclipse Maven repository settings (unsupported HTTPS issue + add Liferay Public Maven Repository settings)
      2. make sure user config.ini file does not override Eclipse local m2 repository
      3. resolve latest Talend Liferay Definitions jar file at Liferay Maven
      4. download and copy to TOS/studio/plugins folder
      5. alter config.ini to activate downloaded definitions
        Challenge1: TOS comes with disabled dependency auto-download - can we ask in dialog and enable it for user???
        Challenge2: what are options if user overrides Eclipse m2? Do we have to tweak user/.m2?

      All other runs:

      1. are crucial settings compromised - https/liferay, repo settings, config.ini
      2. if new component version detected - ask user if update should occur?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matija.petanjek Matija Petanjek
              Reporter:
              igor.beslic Igor Beslic
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:

                  Packages

                  Version Package