Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-26923

Decouple marketplace-nuxeo-duoweb-authentication release version from the installable target version of platform

    Details

    • Upgrade notes:
      Hide

      Build and installation target version are now independent.

      Show
      Build and installation target version are now independent.
    • Sprint:
      nxfit 11.1.7
    • Story Points:
      1

      Description

      Hello,

      When releasing the marketplace-nuxeo-duoweb-authentication we should be able to specify on which plateforme she will be installed.

      it means we should have ability te decouple the target version and the build version used to compare the zip (assembly.xml) when building market place

      For example if we release marketplace-nuxeo-duoweb-authentication 9.10. by using IT-release-on-demand , we will not be able to specify in  OTHER_VERSION_TO_REPLACE :  9.10-HF29-SNAPSHOT/9.10/19.10-HF29-SNAPSHOT. Because the result of that it the presence of two libs of xerces nxr-1.5.4-SNAPSHOT.zip:

      lib/xercesImpl-2.12.0.jar and nuxeo-nxr-server-9.10.zip: lib/xercesImpl-2.11.0.jar

      this caused the the startup error (time out), the presence of two jar is fixed by NXP-26864

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 1 hour
                  1d 1h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.