Bill Shannon wrote:
> Kedar Mhaswade wrote:
>> I had been thinking about this for quite some time, but
>> could not get around to actually do it. At the moment,
>> we have no support for finding out what version of
>> Servlet/JSP or EJB or JPA ... spec a particular installation
>> of GlassFish v3 Prelude supports. We have a "version" command
>> that shows the product version and build ID. We also have a
>> list-modules command that tells us the implementation versions
>> of modules (in /modules folder). To some extent, it gives a
>> misleading output like:
>> Module : org.glassfish.javax.ejb:10.0.0.SNAPSHOT
>>
>> Isn't it desirable to have a command that identifies the
>> spec versions a particular GlassFish Platform installation
>> implements?
>
> Ideally, java.lang.Package would do it. Everyone should be creating
> jar file manifests that include this information.
>
> Much of the same information appears in the manifest in the OSGi headers.
> Sahoo was going to describe the mapping between the two.
>
And don't you think there should be a shortcut for users to get to
this information? Or should users read the manifests?
> Do we really need a CLI command to get at this information?
Not necessarily. We have existing option named --verbose on an existing command
named "version". Traditionally, we have mishandled this command in that
without --verbose, it would give you the full name of the product and
with --verbose it displays the same along with build id (how very verbose!)
I thought I could better utilize this option for this purpose.
The real question I guess is whether we should try to provide an easy
way to satisfy questions like: "Does my GlassFish installation support EJB 3.1"?
I am not sure if UC is going to be handy for this.