As there seems to be demand for 1.4 support, I'll see what I can do. I'd rather not maintain a 1.4 branch, but I can probably reorganize the code in such a way that all of the 1.5-requiring functionality (the use of annotations) is self-contained in a separate bundle. I can possibly mimic the the annotation style in 1.4 somehow.
-jeremy On Fri, Mar 7, 2008 at 3:48 AM, Nektarios K. Papadopoulos <[EMAIL PROTECTED]> wrote: > Hi Jeremy and Ken, > > same here! We've also been thinking something like this but never actually > implement it. Another added benefit for me is that you don't need any > additional > telnet-like OSGi service to give remote access to the framework command > shell. > > But I'm also interested in back porting it to 1.4. Jeremy would you be > interested in creating a branch for this effort? > > -nek > > PS. Is there a mailing list or forum, dedicated to Springfield Command system > discussion? > > > > Jeremy Volkman wrote: > > Hi Ken, > > > > Java 1.5 is required for the annotation style described on the wiki > > (the easiest way to write commands IMO). Other than that, just remove > > the use of generics and for-each loops, and possibly a use of > > Boolean.parseBoolean() and you should be good to go. > > > > -jeremy > > > > On Thu, Mar 6, 2008 at 1:27 PM, Ken Gilmer <[EMAIL PROTECTED]> wrote: > >> Hi Jeremy, > >> > >> This looks very cool! I've also been thinking of something like > >> this (OSGi from shell) but never actually did anything about it. :) > >> Is the Java 1.5 requirement serious, or could it be easily backported > >> to 1.4? > >> > >> thanks > >> ken > >> > >> > >> > >> On Mar 4, 2008, at 1:47 PM, Jeremy Volkman wrote: > >> > >> > Hi all, > >> > > >> > A few months ago we replaced our extensive use of the built-in Equinox > >> > console with our own system. Some of our requirements for the new > >> > system were: > >> > * Multiple user support > >> > * Command history > >> > * Output processing (grep, sort, sed, awk, etc.) > >> > * The ability to execute Equinox commands (start/stop bundles, system > >> > status, etc.) > >> > > >> > Instead of reinventing a very large wheel, we simply placed command > >> > execution in the context of a UNIX shell. > >> > > >> > More detail and examples, as well as the source and binaries, are > >> > available at: http://code.google.com/p/cimspringfield/wiki/Commands > >> > > >> > Let me know if you have any questions or comments. > >> > > >> > Thanks, > >> > Jeremy Volkman > >> > _______________________________________________ > >> > OSGi Developer Mail List > >> > [email protected] > >> > https://mail.osgi.org/mailman/listinfo/osgi-dev > >> > >> _______________________________________________ > >> OSGi Developer Mail List > >> [email protected] > >> https://mail.osgi.org/mailman/listinfo/osgi-dev > >> > > _______________________________________________ > > OSGi Developer Mail List > > [email protected] > > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > > -- > ______________________________________________________________ > Nektarios K. Papadopoulos > Senior Engineer > Home Automation Group > inAccess Networks > ______________________________________________________________ > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
