Hi Christian,
1/ Lukasz worked on some utils to render table in Karaf.
2/ I prefer the osgi:list, it looks more clear for me.
However, I like the version column (it's easier to read). We can split
the current osgi:list name column in name + version.
Regards
JB
On 07/08/2011 12:52 PM, Christian Schneider wrote:
Hi all
while implementing https://issues.apache.org/jira/browse/KARAF-561
I found that I do not like the look of our current table output like in
osgi:list too much.
Currently it looks like this:
ID State Blueprint Level Name
[ 0] [Active ] [ ] [ 0] System Bundle (3.2.1)
[ 1] [Active ] [ ] [ 5] OPS4J Pax Url - aether: (1.3.4)
[ 2] [Active ] [ ] [ 5] OPS4J Pax Url - wrap: (1.3.4)
[ 3] [Active ] [ ] [ 8] OPS4J Pax Logging - Service (1.6.3)
[ 4] [Active ] [ ] [ 8] OPS4J Pax Logging - API (1.6.3)
[ 5] [Active ] [ ] [ 10] Apache Felix Configuration Admin Service (1.2.8)
For obr:list I experimented with the following:
| NAME | SYMBOLIC NAME | VERSION |
| dm Kernel OSGi Spring DM Fragment |
com.springsource.kernel.kerneldmfragment | 2.0.1.RELEASE |
| dm Kernel OSGi Spring DM Fragment |
com.springsource.kernel.kerneldmfragment | 2.0.2.RELEASE |
| dm Kernel OSGi Spring DM Fragment |
com.springsource.kernel.kerneldmfragment | 2.0.3.RELEASE |
I think that looks much cleaner.
What do you think? Even more ideas?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
