[GLASSFISH-18525] No profile info in asadmin version output Created: 16/Mar/12  Updated: 19/Sep/14

Status: Open
Project: glassfish
Component/s: command_line_interface
Affects Version/s: None
Fix Version/s: 4.1

Type: Improvement Priority: Major
Reporter: Cheng Fang Assignee: Snjezana Sevo-Zenzerovic
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to GLASSFISH-19651 Include the svn revision(s) in the Ve... Open

 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.



 Comments   
Comment by Tom Mueller [ 16/Mar/12 ]

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?

Comment by Tom Mueller [ 16/Mar/12 ]

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.

Comment by Cheng Fang [ 17/Mar/12 ]

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.

Comment by Tom Mueller [ 24/Dec/12 ]

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.

Comment by Snjezana Sevo-Zenzerovic [ 15/Feb/13 ]

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

Comment by Romain Grécourt [ 15/Feb/13 ]

linking to another issue

Generated at Wed Jun 03 05:10:58 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.