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

Merge Web UI addons

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 11.1
    • Component/s: Web UI

      Description

      We'd like to have all Web UI code and extensions from addons in a single repository and packaged in a single jar

      Typically https://github.com/nuxeo/nuxeo-dam/tree/master/nuxeo-dam-web-ui html/js resources will move to nuxeo-web-ui repo.

      We keep git history.

      Once the jar is deployed in the tomcat, we need to think of a mechanism to discover which addons are installed to enable their web ui fragment:

      • we iterate in index.jsp over installed addons and load them by convention from the war
        (This would just be a temporary state until Web UI has its own deployment in its own node server).

      About https://github.com/nuxeo/plugin-nuxeo-web-ui, we are also going to merge it into nuxeo-web-ui.

      Final repo hierarchy could look like:

      ├── addons
      │   └── dam
      │       ├── nuxeo-dam-bundle.js
      │       ├── ftest
      │       ├── document
      │       ├── package.json
      │       └── src
      ├── index.html
      ├── package.json
      ├── src
      ├── pom.xml
      └── web-ui-bundle.html
      
      

      Document type layouts

      Our webpack bundling script will have to properly handle these addons fragments.

      mp clean up

      We should end up without any *-web-ui.jar bundle anymore. As a direct result, every mp assembly file should be cleaned up:

      BTW, here is the list of addons that extend Web UI:

      and for test purpose:

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 week, 2 hours, 34 minutes
                  1w 2h 34m

                    PagerDuty

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