Issue Details (XML | Word | Printable)

Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Romain Grécourt
Reporter: abien
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

asadmin list-containers should list the spec version of the container

Created: 29/Aug/08 01:55 AM   Updated: 28/Jun/13 05:37 PM
Component/s: admin
Affects Version/s: V3
Fix Version/s: future release

Time Tracking:
Not Specified


Operating System: other
Platform: All

Issuezilla Id: 5,744
Participants: abien, km, Romain Grécourt, Sanjeeb Sahoo and Tom Mueller

 Description  « Hide

The output of the command asadmin list-containers looks like that in GF 3b20

Container : jpa
Container : web
Container : security
Container : jruby

GF 3 is OSGI based, so potentially more than one container could be active at
the same time or activated / deactivated at runtime. There for the spec-version
should be visible in the listing. Otherwise it is hard for real world projects
to rely on certain functionality and e.g. file bugs.

The command should list something like:

Container : jpa [2.0]

km added a comment - 08/May/09 12:22 PM

Sahoo, the ModuleDefinition currently does not have getSpecVersion and the
MANIFEST.MF does not have Specification-Version attribute. We need to get this

I am assigning this to you so you can decide and update the API so I can call it
from list-containers. Assign it to me when you are done.

km added a comment - 27/May/09 11:16 AM

The right sahoo.

Tom Mueller added a comment - 25/Jan/11 11:48 AM

Cleared the Fix version field since this issue isn't going to be fixed in V3.

Sanjeeb Sahoo added a comment - 23/Mar/11 01:45 PM

It seems like admin folks have to work with build team to have additional metadata in the runtime to provide such information.