in light of feedback from Karaf committers [1], would it be okay to copy Christian Schneider's table printer [2] into the Camel Karaf commands project (org.apache.camel.karaf.commands.internal) as a private utility class, at least until it's available in a Karaf release?
i strongly agree with Claus about striving for neutral modularity, and at the same time Christian explained that this table printer is already small and self-contained. is it an agreeable compromise to temporarily borrow the implementation? [1]: http://karaf.922171.n3.nabble.com/table-printer-for-Karaf-commands-tt3887535.html [2]: http://svn.apache.org/viewvc/karaf/trunk/shell/console/src/main/java/org/apache/karaf/shell/console/table/ ~ Reuben On Thu, Apr 5, 2012 at 12:32, Claus Ibsen <claus.ib...@gmail.com> wrote: > Well I am talking about an end user library which has utility methods so > people can use that in their Karaf commands / plugins. > > The irony is that Karaf is all about modularity. So would it not be > possible to offer a neutral Karaf library that people can use on both 2.x > and 3.0. > > I assume the table and other util methods is mostly about string > manipulation and to make commands output nicely in Karaf. And thus its not > deeply tied to te Karaf container runtime version. So it ought to run on > both 2.x and 3.x. >
