|<< Back to previous view|
[GLASSFISH-18525] No profile info in asadmin version output Created: 16/Mar/12 Updated: 15/Feb/13
|Reporter:||Cheng Fang||Assignee:||Snjezana Sevo-Zenzerovic|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Participants:||Cheng Fang, Romain Grécourt, Snjezana Sevo-Zenzerovic and Tom Mueller|
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
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.
|Comment by Tom Mueller [ 16/Mar/12 09:17 PM ]|
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 09:29 PM ]|
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 03:07 AM ]|
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 08:32 PM ]|
Assigning to Snjezana for the 4.0 release since this is primarily a packaging task.
|Comment by Snjezana Sevo-Zenzerovic [ 15/Feb/13 04:31 PM ]|
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 04:40 PM ]|
linking to another issue