OK, I just updated RIVER-300 <https://issues.apache.org/jira/browse/RIVER-300> with the details that should allow this to build. Basically there were some details that didn't get captured in the original patch due to the way SVN creates patches, which I wasn't familiar with. Sorry, I'm so used to doing everything with git branches and PR's, I've all but forgotten how to use SVN.
Anyway, if you grab that new zip file I uploaded, and extract it in $CHECKOUT_DIR/modularize/apache-river, it should create two new modules "river-logging" and "phoenix-activation". I also renamed on module underneath tools, to what I *think* the original intent was. I'm I'm wrong on that point, you guys can just skip this step and tweak the <module> reference in the pom.xml in tools/ to match the actual directory name. What I did was, in $CHECKOUT_DIR/modularize/apache-river/tools: $> mv computehttmdcodebase/ computehttpmdcodebase Doing that along with the zip file extraction *should* give you something that will compile / package. This is with the aforementioned caveats that the module structuring was hacked up a lot to deal with the circular dependency stuff, and I made no effort to fix up the OSGI stuff, or do anything with the existing unit tests except see that they compile. Phil
