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

Improve Runtime Contributions Error/Debug/Test management


    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Runtime


      Error / Debug

      There are still some cases where Nuxeo Runtime does not behave cleanly and makes debugging harder than needed.

      See NXP-16642: should detect

      • duplicated component name
      • extension point not found
      • missing requirements from non optional components
      • invalid XML contribution
      • missing file referenced from MANIFEST


      When Nuxeo Server starts, in case of error (bad contribution, bad startup handler ...), Nuxeo Runtime should stop right away and display the error if it is a "grave" error or if "strict mode" is enabled.

      Use cases to review, warnings at startup also need improvements, see NXP-17707

      Tests Setup

      Using FeatureRunner is great, but if for some reason there is an error during the setup of one of the feature, the test fails and this is usually very difficult to debug:

      • because it does not say there is a setup issue
      • because the logs and exceptions are swallowed

      -> TODO: give examples


        1. job-shutdown-server.log
          13 kB
        2. server.log
          212 kB
        3. server2.log
          253 kB
        4. signature-server.log
          15 kB

          Issue Links



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


                • Created:


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