glassfish
  1. glassfish
  2. GLASSFISH-18525

No profile info in asadmin version output

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.1
    • Component/s: command_line_interface
    • Labels:
      None

      Description

      Running asadmin version --verbose in GlassFish Web Profile produces the following output:

      Version = GlassFish Server Open Source Edition 4.0 (build cf126330-private), JRE version 1.6.0_26
      Command version executed successfully.

      It doesn't indicate if it's a Web Profile.

      Need an easy to tell if a GlassFish installation is Web Profile, or any other profile, and version command seems the closest fit.

      server.log should also include the same product/profile info. I guess the value furnished to version command is also used for the product info in server.log.

        Issue Links

          Activity

          Hide
          Tom Mueller added a comment -

          The difference between the web and full profile consists of a set of IPS packages, such as metro, appclient, mq, cmp, ejb, and corba. What if just one or two of these packages is installed? What profile should be reported?

          Show
          Tom Mueller added a comment - The difference between the web and full profile consists of a set of IPS packages, such as metro, appclient, mq, cmp, ejb, and corba. What if just one or two of these packages is installed? What profile should be reported?
          Hide
          Tom Mueller added a comment -

          Suggested fix:
          The version implementation on the trunk uses a glassfish/config/branding directory for storing the version information. Currently, glassfish.zip uses a single file, glassfish-version.properties, which has the "GlassFish Server Open Source Edition" string that you see in the output. The version implementation supports having multiple properties files here for use by nested products. This was originally designed for supporting the Open Source Edition vs. Oracle GlassFish Server case. However, this mechanism can also be used to support full vs. web information. Just have two properties files:

          glassfish-web-version.properties:
          product_name=GlassFish Server Open Source Edition (web profile)
          abbrev_product_name=glassfish_web

          glassfish-full-version.properties:
          product_name=GlassFish Server Open Source Edition (full profile)
          abbrev_product_name=glassfish_full
          based_on=glassfish-web

          The first file can be delivered with the glassfish-web-profile package. The second can be delivered with the glassfish-full-profile package.

          Show
          Tom Mueller added a comment - Suggested fix: The version implementation on the trunk uses a glassfish/config/branding directory for storing the version information. Currently, glassfish.zip uses a single file, glassfish-version.properties, which has the "GlassFish Server Open Source Edition" string that you see in the output. The version implementation supports having multiple properties files here for use by nested products. This was originally designed for supporting the Open Source Edition vs. Oracle GlassFish Server case. However, this mechanism can also be used to support full vs. web information. Just have two properties files: glassfish-web-version.properties: product_name=GlassFish Server Open Source Edition (web profile) abbrev_product_name=glassfish_web glassfish-full-version.properties: product_name=GlassFish Server Open Source Edition (full profile) abbrev_product_name=glassfish_full based_on=glassfish-web The first file can be delivered with the glassfish-web-profile package. The second can be delivered with the glassfish-full-profile package.
          Hide
          Cheng Fang added a comment -

          If the original installation is Web Profile, I think it should remain a Web Profile product even after adding certain modules later. There is no guarantee that adding modules will make a Web Profile product into a different profile product.

          Show
          Cheng Fang added a comment - If the original installation is Web Profile, I think it should remain a Web Profile product even after adding certain modules later. There is no guarantee that adding modules will make a Web Profile product into a different profile product.
          Hide
          Tom Mueller added a comment -

          Assigning to Snjezana for the 4.0 release since this is primarily a packaging task.
          The intent is to implement the suggested fix. When the package that contains the glassfish-full-version.properties file is installed, then the version command will report it as the full version regardless of what other packages are installed.

          Show
          Tom Mueller added a comment - Assigning to Snjezana for the 4.0 release since this is primarily a packaging task. The intent is to implement the suggested fix. When the package that contains the glassfish-full-version.properties file is installed, then the version command will report it as the full version regardless of what other packages are installed.
          Hide
          Snjezana Sevo-Zenzerovic added a comment -

          This is more of an RFE than bug at this point. Deferring to 4.0.1 given time and resource constraints.

          Show
          Snjezana Sevo-Zenzerovic added a comment - This is more of an RFE than bug at this point. Deferring to 4.0.1 given time and resource constraints.
          Hide
          Romain Grécourt added a comment -

          linking to another issue

          Show
          Romain Grécourt added a comment - linking to another issue

            People

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

              Dates

              • Created:
                Updated: