Remy Maucherat wrote: > As was discussed a while ago with Costin and a few others, it appears > that the daemon API is inadequate, and a refactoring is proposed. > > The reorg is: > - Removal of the daemon API (org.apache.commons.daemon), to be replaced > by pure introspection. The rationale for this was discussed with Costin > at the time. > - Creation of a commons-launcher component to host the launcher code now > used in the upcoming Tomcat 5. It turns out the merge with Ant will not > happen in the forseeable future, and the functionality is useful in > Tomcat, so I think we should keep the code in the commons, and wait for > it to be "picked up" :) > - As a consequence, the "daemon" module will be renamed to "launcher". > It is also proposed that the resulting module be moved to commons proper. > > <ballot> > +1 [ ] Yes > -1 [ ] No:
-1 : That is more than one element! I am -0 replacing the daemon API by introspection. I am +1 for creating a commons-launcher component for Tomcat 5. I am -1 renaming daemon to launcher. The initial goal of org.apache.commons.daemon is to run JAVA services not only to start Tomcat. There was a JSR96 (http://www.jcp.org/jsr/detail/96.jsp) is there any new JSR on a similar topic? The daemon code has been moved for jakarta-tomcat to jakarta-commons-sandbox/daemon moving it again does not seem a good idea. I use daemon in several places: - To start an embedded Tomcat. - To run Tomcat on port 80 as user nobody. - To start "services" on win98. > > > </ballot> > > Remy > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
