glassfish
  1. glassfish
  2. GLASSFISH-20333

Stray package prototype file included in GlassFish distribution

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0_b84_RC1
    • Fix Version/s: 4.0_b86_RC2
    • Component/s: packaging
    • Labels:
      None

      Description

      IPS based GlassFish distributions contain stray glassfish/pkg_proto.py file. pkg_proto.py file belongs to glassfish-common-web package. It looks like something may be off with assembly descriptor and file does not get filtered out.

        Activity

        Hide
        Snjezana Sevo-Zenzerovic added a comment -
        • What is the impact on the customer of the bug?

        It is a regression compared to previous releases. While it is not directly affecting functionality, it is quite visible and may introduce some confusion for the end user.

        • What is the cost/risk of fixing the bug?

        Low risk. File is not getting filtered out during package content staging so assembly descriptor file needs to be updated.

        • Is there an impact on documentation or message strings?

        No.

        • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?

        Regular GF testing is sufficient.

        • Which is the targeted build of 4.0 for this fix?

        b86

        • If this an integration of a new version of a component from another project,
          what are the changes that are being brought in? This might be list of
          Jira issues from that project or a list of revision messages.

        N/A

        Show
        Snjezana Sevo-Zenzerovic added a comment - What is the impact on the customer of the bug? It is a regression compared to previous releases. While it is not directly affecting functionality, it is quite visible and may introduce some confusion for the end user. What is the cost/risk of fixing the bug? Low risk. File is not getting filtered out during package content staging so assembly descriptor file needs to be updated. Is there an impact on documentation or message strings? No. Which tests should QA (re)run to verify the fix did not destabilize GlassFish? Regular GF testing is sufficient. Which is the targeted build of 4.0 for this fix? b86 If this an integration of a new version of a component from another project, what are the changes that are being brought in? This might be list of Jira issues from that project or a list of revision messages. N/A

          People

          • Assignee:
            Snjezana Sevo-Zenzerovic
            Reporter:
            Snjezana Sevo-Zenzerovic
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: