Christian, Yes, I agree eventually we will put this into the package.html. Hopefully as we get the maven build working we will be building the javadocs as well.
In terms of logging, this struck me as add also. On thing to remember though, is that a lot of the code is compiled by GWT into javascript code. So code that is common between the server and the client, can only make use of libraries that are available on the client side. Log4J is not available in the browser. So it looks like a simplified logging mechanism was added that would work in both cases. ~Michael On Jun 26, 2012, at 7:43 AM, Christian Grobmeier wrote: > Interesting insight. > > I think this information should also go into package.html. > > Besides, I have two questions: > > - why isn't the apache namespace aka org.apache.wave.* used? > - i see much packages containing logging stuff. Why is it there? Are > there any special needs which requires implementing custom stuff > instead of using tools like log4j 2 or slf4j? > > Cheers, > Christian > > On Tue, Jun 26, 2012 at 12:28 AM, Michael MacFadden > <[email protected]> wrote: >> All, >> >> In an attempt to build a sensible maven structure and to start to document >> our code base, I have started working up the following table: >> >> https://cwiki.apache.org/confluence/display/WAVE/Source+Code+Organization >> >> If people can review and comment that would be great. >> >> ~Michael > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de
