Uploaded image for project: 'Struts 1'
  1. Struts 1
  2. STR-1967

Provide more version number granularity in manifest.mf

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.1.0
    • Fix Version/s: 1.3.0
    • Component/s: Build
    • Labels:
      None
    • Environment:
      Operating System: All
      Platform: All
    • Bugzilla Id:
      26677

      Description

      As a vendor implementing Struts Support into our IDE (Oracle JDeveloper) it
      becomes important that we can detect exactly which version of Struts is
      available and do the right thing accordingly.
      The situation with 1.1 was an example of this. There are DTD changes between the
      final version and preview betas, but the manifest in both cases just has 1.1 as
      the Implementation-Version.
      I see from the nightly builds for 1.2 that the minor version is now being used
      but is set to 0, e.g. 1.2.0.
      Ideally a more granular numbering scheme should be adopted for 1.2, even down to
      the level of nightlies being identified using a _suffix to the minor build
      e.g. 1.2.<milestone>_<nightly> for a nightly build
      1.2.<milestone> for a stable RC or Final

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              duncan.mills@oracle.com Duncan Mills
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: