Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-38808

WebResourceManager is deprecated, but its javadoc provides no reasonable replacement.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Answered
    • Low
    • None
    • 6.2.6
    • None

    Description

      JIRA 6.2.6 uses the 3.0.0-m24 version of the Atlassian plugins webresource library, in which WebResourceManager is deprecated.

      The suggested replacement is WebResourceAssembler, but that class cannot be injected as WebResourceManager can, nor does it have a method that replaces WebResourceManger.requireResource(String resourceID).

      It is suggested that PageBuilderService can be used to get the current WebResourceAssembler, but assembler() is an instance method and PageBuilderService cannot be instantiated with new, nor can it be injected.

      These issues may all have something to do with the fact that version 3 of the Atlassian plugins webresource library has not been released yet. The version number of 3.0.0-m24 suggests that this is a development build, as does the absence of any version beyond 2.9 from the Atlassian developer documentation web pages.

      I suggest that either
      a. A production version of JIRA should depend on a production version of the webresource library rather than an unreleased and as-yet incompletely documented development build, or
      b. The required managers be made injectable and methods with equivalent functionality to the deprecated ones be added, and the javadocs updated to reflect this, or
      c. WebResourceManager have the @deprecated tag removed until a reasonable replacement becomes available.

      I favor (a) as this should require just altering the relevant POM to include the production version of the webresource library, and in that version WebResourceManager is not deprecated. Additional code and documentation changes would be required to make (b) work.

      If (a) won't work because JIRA 6 depends on new functionality from webresource 3.0, then I would favor (c) as a stopgap instead.

      Attachments

        Activity

          People

            Unassigned Unassigned
            edba5219f666 Daniel Hankins
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: