There is only one Daemon release in the Maven repo as far as I can make out - 1.0.1 - which is from way back in Jakarta time.
AIUI, there are no plans to make any further releases to Maven repositories, because the component is not really useful as a Maven dependency. However, the groupId is currently commons-daemon, which is not ideal. So just in case a Maven release is ever considered in future, I think it would be worth changing the groupId now to org.apache.commons. As far as I can tell, this will not affect anything else, as there should be no Maven dependencies on Daemon. Nor should it would not affect Daemon itself. WDYT? S/// --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
