Hi Ioannis, The "problem" is there, but I don't consider as a problem, just a change ;)
For instance, the annotations (like @Command) are no more provided by gogo but directly by Karaf (like org.apache.karaf.shell.commands.Command).
But, if a 3rd party application uses gogo annotation, it should still work in Karaf as Karaf still use gogo runtime (I have to check).
Let me take a look. Regards JB On 01/30/2013 12:11 PM, Ioannis Canellos wrote:
I am not sure if this is still the case, so please forgive me if the problem no longer applies, but it seems that all 3rd party projects that provide Karaf commands, can't possibly have a bundle that will work both 2.x and 3.x. This is mostly due to the fact that in 3.x we no longer provide or use the gogo annotations for commands, options and arguments. Unless we manage to solve this one, all projects that provide integration with the karaf shell would need to rewrite their commands for 3.x, which is a bit annoying if not frustrating. So, I was wondering: is it still an issue? is there a workable work around this? are there additional issues that will totally break compatibility and thus there is no reason to put any effort on this one? should we rethink about dumping the gogo annotations?
-- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
