Thanks Henning ( and other recent T2 committers)...! It is great to see some development happening on Turbine. Now that T2 seems to be going somewhere, I may try and get some of my own fixes/patches committed.
First Up: I have been playing around with Jetspeed, and working with The Tutorial. In Jetspeed is a great method of maintaining your own TR.props values, while still being able to deploy to a plain vanilla installation of Turbine. (Might help upgrade headaches!). Basically you put your props in your own MyTR.properties, and then those are merged into the vanilla TR.props. Here is a link: http://www.bluesunrise.com/jetspeed-docs/JetspeedTutorial.htm#_Toc26987080. Currently it is just a java class, but I could wrap it up in an Ant task if this looks like something useful. Eric Pugh -----Original Message----- From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 19, 2002 7:30 PM To: [EMAIL PROTECTED] Subject: Logging and Configuration committed to Turbine 2.3-dev Hi, as promised, I just committed the two major changes for post-2.2 turbine, that I intended to do. The code still compiles for me and passes some basic tests. :-) I tried to separate the configuration stuff from the logging, but the code isn't only almost inseparatable, it was also very difficult to untangle the Fulcrum Service Broker stuff (yeah, yeah, I know. Plexus) from the patches, so I decided to commit all three parts in a row, basically because this code works stable for me since about five months. Major user visible changes: - TurbineResourceService and TurbineLoggingServices are _GONE_! Remove all references to the logging from your TurbineResources.properties Remove all Logging Statements from your properties - Logging is now Log4j based. You need a separate config file. I intend to make it possible to fold this into the TR.props, but the code isn't here, yet. An example Log4j.properties File has been checked in, too but there might be some changes to the maven files necessary so that it gets installed automatically. Patches and Commits welcome! - The Service Broker now knows about "earlyinit" like the fulcrum Broker. I intend to write a short "howto change from the old Turbine TurbineResources / Log structures to commons-logging / commons-configuration. But not tonight. If you have questions or your code breaks, please tell me. I factored out this code from a _much_ larger patch and I might have forgotten a part. As I said, the code still compiles for me (BTW: You do need the current HEAD from commons-configuration, which builds the commons-configuration-1.0-dev-2.jar If you don't have it / if it isn't on ibiblio, please, someone put it there. Thanks). I do have a lot of faith in this code (as I said: I'm running this since about five months without trouble) and after some shakedown is done, I will tag a branch tag for checking in my Turbine-2 / Fulcrum patches. Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED] Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED] D-91054 Buckenhof Fax.: 09131 / 50654-20 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
