I've committed some work yesterday around mavenizing gogo. I've split it in several parts for now: * runtime: contains the apis and the implementation of the two main service (threadio, commandProcessor) * console: this module contains the basic stdio console + telnet stuff which is currently not used * launcher: supposed to be able to be used without osgi to actually launch the framework (status unknown)
I see several options: * keep the current split and maybe move the telnet stuff in its own module * refactor into a single bundle and use properties from the bundle context / config admin to decide wether we need to launch the console and / or telnet Also, there is an emulation layer for equinox which is currently not used. We need to either find a way to activate it (maybe through properties too) and maybe write another one for felix to emulate the set of commands provided by the shell subproject ... Feedback welcome. On Mon, Jun 22, 2009 at 17:27, Guillaume Nodet<[email protected]> wrote: > Unless someone objects I'll start working on gogo to: > * create a pom > * modify the structure to fit maven conventions > * rename the aQute package to org.apache.felix.gogo > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
